Does a desktop display utility need to worry about EAC detection?

I maintain a small open-source Windows display utility that is like a all in one combo of QuickResolutionChanger, VibranceGUI and windows calibration. It changes refresh rate through ‘ChangeDisplaySettingsExW’, digital vibrance through ‘NvAPI_SetDVCLevel’, desktop gamma through ‘SetDeviceGammaRamp’. And an optional puller that uses ‘CreateToolhelp32Snapshot’ to notice when the application holds focus so it can switch profiles. Source is MIT and public.

It opens no handle to any game process, reands and writes no external memory, injects nothing, hooks nothing, draws no overlay, and no auto inputs. Every value it writes is one that the Nvidia Control Panel or windows settings already exposes, but its faster and more convenient.

My question: Can this cause issues with the EAC anticheat, is there anything in the call list that is a problem? I would rather cut features than leave my users guessing, i have already removed the puller.

Any answer is helpful even a here we don’t discuss this is!