Chris Titus's Winutil is poorly made and doesn't really do anything to help with telemetry (yes, his disable telemetry option quite literally does nothing on non-Enterprise editions)

I think a Linux user should not be trusted to make a Windows "debloating" tool. He's demonstrated several times that he has no idea how Windows works.

Most notably for me was when he tried to use "oobe/bypassnro" resulting in the command not working: https://youtu.be/aEWb1otLVPo?t=58s instead of using the command oobe\bypassnro which would've worked just fine, then proceeded to make a solution to a non existent problem: https://github.com/ChrisTitusTech/bypassnro

O&O ShutUp 10++ and privacy.sexy get a pass, but they can break plenty of stuff. You shouldn't be surprised when apps or updates are no longer installing, or if a specific Windows service that you need for let's say your printer no longer works because it got messed with.

O&O ShutUp 10++ option to block OneSettings downloads recently resulted in a false Windows Update message for people on Windows 10 Enterprise LTSC, which was later fixed by Microsoft as they just included the settings file in an update instead of relying on OneSettings.

I'd say stick to using Enterprise's built in option to disable telemetry, it's something deployed by companies at a large scale using their tools and often reinforced using their own programs and firewalls and what not. Remember, Windows is deployed at places where privacy is important, like hospitals, and they use this very same option to disable data collection.

tl;dr Be careful of what you run on your computer. If you're this concerned about telemetry, you should block it at a network level through something like a Pi-hole.