Restrict CPU core sharing for renderer process

This policy helps mitigate side-channel cross-process memory attacks by isolating the renderer process to a dedicated CPU core, preventing other processes from being scheduled on the same core. This mitigation is supported on Microsoft® Windows® 11 24H2 and later. If the operating system doesn't support the necessary scheduling features, this policy has no effect. Enabling this policy may reduce performance in demanding workloads, similar to the impact of disabling hyperthreading. For more information, refer https://learn.microsoft.com/windows/win32/api/winnt/ns-winnt-process_mitigation_side_channel_isolation_policy
If you enable this policy, other processes can't be scheduled on the same CPU core as a renderer process.
If you disable this policy, other processes can be scheduled on the same CPU core as a renderer process.
If you don't configure this policy, other processes can be scheduled on the same core as the renderer process. Behavior can vary depending on Microsoft Edge version and platform.