The correct way to do this is to use Local GPO to modify the value for all existing and future users, not to try to directly edit the current user hive, which does not actually exist in the context of the agent.
There is ways to manipulate the hive for the currently logged in user only, but still, it is best to use LocalGPO to achieve this.
Any solution that doesn’t use Local GPO will only work if a user is currently logged in and only for that hive, unless you loop through and make the change for all users.
Even if you loop through and make the change for all users, that will then not take affect if a new user logs into the system that did not have their hive loaded when the change was made.
Thus the only way to ensure per-user registry changes is to use LocalGPO.
The only reason you might NOT want to use LocalGPO is if you want to allow users to change this setting themselves to whatever they want, but you only want to set a default value but allow them to change it later. If you want to force this to be enabled and not allow users to disable it, then LocalGPO is your best option.