Dead links abound: https://developer.mozilla.org/en-US/docs/Mozilla/Gecko/Embed...
Scary warnings: https://developer.mozilla.org/en-US/docs/Mozilla/Gecko/Embed...
This choice (under Gary Kovacs, IIRC) has effectively made it a poor choice for _anyone_ to build on top of Mozilla's browser engine without forking the entirety of the mozilla tree. You'd need to have a very good business justification for attempting it.
Since Chrome is essentially a superset of Chromium, it's been obvious how to build your own equivalent of Chrome (and first-party supported!). There is no "Firefoxium" version of Firefox, and I'd expect developers would need to go to great lengths to keep their code up-to-date on top of mozilla-central.
Creating a new gecko-based product is not very hard, even if you will hit some cases of the platform depending on firefox that you'll have to workaround or borrow.
Creating a full new blink-based product is as difficult actually. Most chromium derivatives take the simpler road of forking chromium, not building a new blink-based browser (eg. Brave maintains a pile of patches).
I don't understand why you would expect a "firefoxium": there is no such thing because there is no proprietary version of the open source Firefox. If you fork Firefox, you're in the same boat as people forking chromium in terms of complexity.
geckoview is also such a product, well hidden behind the android glue :)
Heck, Apple's car will be a Kia.