Then name them! It is literally my job to help developers interface with and be heard within Mozilla.
And then there also is the issue that mozilla has limited resources. So even if you wanted to help you can't help everyone.
This does not exist in the old extension ecosystem or in regular software development. You don't have to beg anyone to please spend time a particular usecase.
It may be painful to get things working yourself, but at least it's an option you have.
Here's an example of users helping each other without needing to petition for support from orbital HQ: http://stackoverflow.com/questions/36927096/firefox-command-...
If this use case is important to you, please file a bug explaining your needs and/or fill out the survey at https://wiki.mozilla.org/Add-ons/Contribute#Improve_add-ons_....
However, there are many extensions that won't be possible in the new extension environment and they will die a silent death as they don't have cheerleaders who can force Mozilla to accommodate them in the new webextension plans; I know one or two such extensions myself (don't use them personally, so I may be wrong, may be not). This forced euthanasia of extensions make FF ecosystem poorer, and FF just another Chrome wannabe.
The point is, Mozilla should show the traits of leader; criticism still has merit whether Vimperator work or not.