And the openHAB demo is here:
With a discussion of what to include in it here:
For most people, I think this would address your original statement.
Don’t get me wrong, I appreciate your willingness to contribute, but it would be better to first look for how the community has addressed this before declaring that you have the solution. 
As for your code, I don’t think it’s a terrible idea, but I’m not convinced its necessary. Virtual items are already possible in openHAB (they just don’t have any channels). And more often than not, people who find openHAB already have hardware that can be controlled by it. If they don’t, it’s easy for most to pick up an inexpensive WiFi outlet. For someone new to home automation, the real magic is when you press a switch on your computer and an actual, physical device toggles on or off.
I’d encourage you to take a look at the demo and revive the thread if you have ideas. Your perspective as a new user is valuable. If you weren’t aware of the demo, maybe we need to do more to promote it.
While text-based configuration is still viable, a lot of effort is going into a GUI that can serve both programmers and non-programmers. As you’re likely aware, it’s not easy to develop any interface that can satisfy both new and advanced users, and many of us are still figuring it out as we move from OH2 to OH3.
I’m not going to tell you that you should use the GUI (I’m only using parts of it), but the ideal is for new users to start with the GUI and then grow into the system. So, efforts need to go toward improving the GUI, not pushing users away from it just three months after its release.