I admire your skill and determination. You must be logged into Joomla R&D.
Recently, Joomla has been going some where wrong.
And you could change it
Yes, this is very interesting code. But why can't I see this on joomla.org?
And it seems to me: it is best to use original libraries, without any "covers". Because as a result we need to know both APIs. And each "COVER" limits the original library and adds its own bugs.
about "helix-bootstrap" it seems to me: each component should move all the libraries it uses into its own namespace and add them to its software. (unless it's a very simple component). CMS collects a lot of software from many developers. And yes, the resulting CMS will be heavy and big. But as a result, we will have a lot of software with great opportunities for end users!
And it will work every time. And this software will be reliable and simple for the end user.
All developers have their own ideas about how things should look and work.
- when clients can't find settings to enable/disable any library - they just don't want to check these settings. The program should work always and everywhere.
- when other developers remove all libraries from other developer - which they use it. To avoid conflicts with your own library
- when developers modify an external library for personal purposes. And others see the standard library but cannot use it.
Yes, it's great to have several popular libraries in Joomla core. But all developers want more features, and they ask for extended libraries. As a result: Joomla doesn't use "popular libraries" because they have a very simple and lightweight interface and others can't use them - because they don't give them all the features they need.
Joomla should be simpler and not change its API every time. After each such change, Joomla lost developers, lost software and lost customers.