Shouting is easy, doing so isn't.
I gave up on trying to maintain forks of web browsers, because their extension API deliberately doesn't allow modifying response bodies. It's just impossible to maintain any fork of any browser because of the sheer amount of features that rely on JS APIs for websites and the amount of commits upstream.
Ad Blockers are just a dirty hack that completely relies on Chromium respecting the Content-Security-Policy headers for all domains. If Google decides to blocklist their own domains for HTTP header modifications, we're fucked. Quite literally.
That's the reason why I kinda started to build my own browser (without a rendering engine for now) that focusses on filtering, parsing, and peer-to-peer offloading traffic and sees itself as a mixture between web browser, scraper and proxy that can be used as a cache for others. It has the idea to act as a web filter service + a webview to render its UI rather than being a render engine and document engine. [1]
I hope that with this market niche there's a way to make this kind of effort sustainable for the future, because all other web browser fork projects I've seen so far are dying off due to no funding and too much work to maintain the codebase.
It's just not feasible to compete in the everday user's browser market. Lots of companies have tried, and lots of companies have failed.
[1] https://github.com/tholian-network/stealth
Edit: Clarification of Chrome vs. libchromium