“anything Google” isn’t really a threat model, and only really comes from “degoogling” nonsense. You can use any Chromium based browser and not have anything to do with other Google products. Google is not the only advertiser on the internet so as far as privacy is concerned hyperfocusing on a single company over all others will lead to unaddressed issues in a threat model where advertising and tracking are primary concerns.
In the case of ungoogled chromium they disabled CRLsets which are more likely to protect you in the case of a rogue CA.
You can determine these things through other fingerprinting methods so this really doesn’t add much in the way of protection. Ungoogled chromium doesn’t provide any fingerprinting protection eg. nothing to do with Canvas etc.
Using ungoogled chromium doesn’t mitigate that, you’re still largely using Chromium with a few patches on top.
You can also determine the same information through JS fingerprinting libraries creepjs so that doesn’t help you. Disable JS? Sure, but most websites won’t actually work like that.
All browsers are fingerprintable, it’s just that Brave and Firefox does more to address that. The very fact that ungoogled chromium users are so few is a fingerprintable metric.
Nonsense. If a browser is good for one thing, it’s good for another thing. Inserting the word “opsec” doesn’t give what you’re saying any credibility.
I would bet 99.9% of people do not compile that source, given how long it takes to build Chromium.