Hi Guys, I honestly did not expect so many of you to jump in and try to help so fast. In the future if I need help I will try to explain the use case a bit as @bernhard suggested.
But just like everything else with Processwire, the solution was way simpler than I even hoped it to be. A big Thank You you @teppo, you did understand me, cause your suggestions were exactly what I needed and solved my problem.
Just in case the use case is still relevant:
The normal roles systems of PW has always worked well for me as it is, and in some sensitive data systems, i have come to rely heavy on PW permissions in systems where I was the only one who needed to add fields and templates and everyone else was only for data viewing, entry and editing. However I have one case now where I want them to be able to build their own PW form in the backend to register incoming data, because then I get to do only the fun part: 1: spinning up VMS, Virtual hosts and clean PW installs and then 2: writing the scripts for reports and graphs from that data.
Basically with this now in my systems, I can use PW the way I used MS Access back in the days. I train the datacollectors to build their own datacollection tools, and I focus on reporting, without the risk that a malevolent other super user can remove me or uninstall the Versioning Module.