Ah, ok.

Still, if the Brave team is expecting to profit through some mean, which is what I theorized, to stop the project from facing losses without completely shifting strategies would usually mean cutting parts of the project that bleed the most money as contingency.

In Firefox's case, I'd say the scope is another. While Brave markets features, Firefox from what I can tell markets simplicity and modularity, even if both point to safety. So if Firefox gets bloated, it strays from its purpose and "betrays" their usebase. If Brave gets bloated, as long as they go in the line of "features for the users' safety", it should still be in line with their initial pitch.