Exposes the SDK runtime to the global scope. Don't use this unless you know what you're doing.
I have to point out that the entire reason there are separate scripting APIs is so we can update them separately. For example we can overhaul the engine without breaking projects using scripting. Exposing the internal engine classes to scripting completely undermines this and risks causing compatibility nightmares. A worst case scenario is that so many people use this, that we cannot implement major new features or optimisations because it would break too many projects. I can't stop you publishing this addon, but I must strongly advise that nobody use this.
This wouldn't be necessary if it was exposed already but not documented, it's totally understandable your point, but indeed it's our own fault if something breaks in our project because we are using it, still please consider making it available but not documented :)
Some things are not documented for a good reason (e.g. we intend to remove it), and other things aren't yet supported for a good reason (e.g. we intend to overhaul the feature before adding APIs for it).
I completely agree and this addon was designed to be confusing for anyone who wouldn't explicitly know the implications of using it.
As an additional precaution, I have marked it as deprecated to refrain too many people from using it mindlessly.
And, just to be clear, this is mainly to be able to do things that the current scripting runtime doesn't allow for, while waiting for it to get updated.