Removing Client Hints on Chromium, More or Less Fingerprintable?

Questions
1

By default, Chromium sends Sec-CH-UA, Sec-CH-UA-Platform, and Sec-CH-UA-Mobile with every request. High-entropy hints (like architecture, model, platform version, etc.) are only sent when a site includes an Accept-CH response header. (They’re also available via NavigatorUAData API but my concern here is specifically the request headers, since that can be blocked more easily.)

Does removing or minimizing these default Client Hints make a browser more fingerprintable (because it deviates from the expected baseline) or less fingerprintable (because it reduces entropy)? And how common is the Accept-CH header in the wild, actually being abused for fingerprinting in practice?

2

If 99.9% of users have it on, probably still more despite the entropy (there’s more of a chance of you blending into a crowd of arm64 Mac users for example than chromium users with client hints disabled). If you’re worried about it, you’re better off using a browser that has it off by default like Mullvad or Tor Browser, among their other strong fingerprinting protections. I’ve balanced the disposable nature of these browsers with staying logged into a set of sites I trust by basically replacing Brave’s private window with Mullvad browser and I’m quite happy with the setup.