Another uphill struggle is cloudflare. Get ready for sites being unavailable because of CF, and endless captchas that make you wonder if they even work.
This would be an excellent opportunity for CF to assert a commitment to a secure and private web by propping up one of the FF forks, even a little bit, and simply make sure it's not auto-killed by their managed policies.
Obviously if a customer wants to manually kill it, it's on them, but CF has a lot of power in choosing defaults.
As someone who cares about privacy, knowing that the company that MITMs a massive chunk of my TLS traffic to websites also controls my browser's funding would make me feel uneasy.
My experience is that anything that tries to tamper with the UA will send CF into a frenzy.
My regular firefox instance is pretty much okay. Unfortunately there is a bunch of super popular crapware shit like Teams and Slack that refuses to properly work on Firefox, unless you tweak the UA. The last time I had to do this was about half a year ago, but Slack refused to let me "huddle", unless I changed my UA. Same with Teams, it straight up said I need to install chrome if I want video chat.
Any time I forgot to change back my UA, CF would not let me in anywhere. I got the captcha, clicked on it, it said "all good", reloaded the page, and I got redirected back to the captcha. Endless loop.
Obviously if a customer wants to manually kill it, it's on them, but CF has a lot of power in choosing defaults.