I maintain a small open-source Windows display utility. It changes resolution and refresh rate through ChangeDisplaySettingsExW, digital vibrance through NvAPI_SetDVCLevel, and desktop gamma through SetDeviceGammaRamp. An optional poller uses CreateToolhelp32Snapshot to notice which application holds the foreground so it can switch profiles. Source is MIT and public.
It opens no handle to any game process, reads and writes no external memory, injects nothing, hooks nothing, draws no overlay and synthesises no input. Every value it writes is one NVIDIA Control Panel or Windows Settings already exposes.
My question for anyone from Epic: does that call surface put a third-party process in scope for EAC detection in titles using your anti-cheat? If any single call in that list is a problem, I would rather cut it than leave users guessing. I have already removed gamma control and the foreground poller from current source.
If Epic does not discuss detection behaviour with third-party vendors, saying so is a useful answer too.