For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions.
What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151.
Mozilla thought it would be a great idea to install AI features in Firefox and that brilliant decision may be causing your issue. Those AI features use an absurd amount of resources on some websites and when they're enabled on my laptop, FF regularly shows ~50% CPU.
When all that BS is turned off CPU use drops to less than 2% most of the time. Search for "AI Controls" in settings and try shutting them all off.
I don't feel bad for people who whine about "well, I have to go into the settings and change a thing". How much did you pay for that browser again? Complacency is what keeps people in abusive ecosystems. Don't be complacent or you're part of the problem.
I'm having trouble making any sense of your word salad. Are you triggered because someone dared criticize a bonehead move by Mozilla, or are you upset that anyone's using Firefox's "abusive ecosystem" in the first place? Neither? Both?
Firefox has lost nearly all of their users and now has less than 4% of the market. Adding a "feature" that makes computers virtually unusable without any indication as to why is yet another reason that's happened. Nevertheless, if poor implementation of a feature makes for an "abusive ecosystem" it means that by your definition all software is part of an abusive ecosystem.
I don't trust at all that that setting stops AI features from using resources. They even go out of their way to say the features are 'blocked' instead of something more confidence-inducing like removed or uninstalled.
I did my testing before the AI features were implemented, and I tested a variety of custom profile settings for firefox (and floorp and librefox) and custom chrome flags for ungoogled chromium (and brave)...
Granted, I was using benchmarks, but the differences are somewhere around 15-30% on my machine on Arch
Edit: These are the benchmarks I ran
Interesting running those... Haven't had to worry about benchmarks on my system, both Chrome and FF are plenty fast. I do wonder how the performance of Chrome with ads would compare to Firefox with the same ads blocked? Every once in a while I use some one else's computer and can't believe how many animated ads show up on pages I frequent.
Do you just put up with the ads or block them another way?
MV2 has always worked on ungoogled chromium, so I just use uBo. I agree with most folks that ads are not an option XD
Have you tried tweaking user.js?
Yes I've used a variety and rolled my own. Tbh the differences are difficult to measure