If I was a betting man which I'm not so I'll just guess ... there's a corporate policy controlling this setting. It might be Active Directory or Mobile Device Management or some other management software. If so, to confirm the policy is controlling the setting you have to move/remove the device out of the jurisdiction of the policy. i.e. move it to a test OU in Active Directory that is not under the control of the policy or some similar action applicable for other management software. I'm not in the game anymore so I cannot keep up with all the myriad software device management schemes etc. also "Intune" is another way to screw up on a mass scale err... I mean manage device settings...
you could talk to "people" in charge of policies ... yeah, like that will be satisfying
once you've confirmed it is controlled by policy then you have to set about getting an exception implemented.
if this isn't the case I have no idea.
given that these are "security" settings it probably came down from the security department so good luck getting that changed. Those guys live in another world and your device/application performance is not a concern.