What do Firefox implementation details have to do with this?

They are modernizing the browser by replacing pieces over time. That's relevant to the topic of browsers being built on legacy tech.

I don't see how this supports to the argument that you can easily build a new, competing browser by forking. If you fork and then need the same kind of resources to replyce the forked codebase with your own, I don't see what you'd win.