The security model used in Firefox OS to gate access to these APIs was very different. We never exposed these web bluetooth to the web at large, only to signed apps.
Mozilla needs to step up and find ways to expose such APIs though, because they are useful. Just saying "no" without proposing a solution is a sure way to lose. There's a bit of hope recently with the implementation of WebMIDI in Gecko.
The overarching theme of your writing on this topic is that Chrome can just spit out Web 'features' at random and unless Firefox implements all of them immediately it is dying. I hope you can try to understand that not only is this not an accurate assessment, but maybe also that Firefox has value beyond being a copy of Chrome.