Nope. The vast majority of web pages and web apps do work either on page load, or in direct response to user input. While in the background, they almost universally sit idle. Multicore has no benefit in this scenario.
The exceptions are games and media, but music is the only case there where you are likely to have something actively running in the background. Unfortunately, audio decoding is so incredibly cheap now that the gains from using a separate core are negligible.
Just that a multiprocess architecture may not be the only way to solve the problem, and if Firefox devs believe they can provide equivalent stability without switching to a multiprocess architecture, I won't ding them just because they can't tick a checkbox that Chrome ticks.
Google (and Microsoft) argue that using processes make the browser more stable in the sense that if one tab crashes, not the entire browser crashes, too (correct, as long as no deadlock in IPC between the processes occur - which has happened in some past Chrome relases) and makes the browser more secure (but not everybody agrees here). Thus they argue that the overhead of processes over threads is worth it.
But if you just want the scalability there are more easy solutions.
Chrome and other browsers of course work hard against that: There is a second fast parser which heuristically finds ressources to preload and Chrome just switched to blink in order to do the parsing and something else in parallel and now they want to do CSS calculations in threads, too, which is hard. There was a story here about it recently: https://news.ycombinator.com/item?id=5895729
The effect of this is pretty obvious with chrome vs. FF: chrome memory usage grows a lot faster with multiple tabs than FF's memory usage does. OTOH, it's easier to manually control usage in chrome by killing tabs. Which of these effects is more important depends on your needs (so I tend to switch between chrome and FF...).
Anyway, anybody claiming that chrome is "obviously" better than FF these days is on crack. They are both very good, and each has its strong points and weak points, but they're pretty much on par...