Non Destructive Booleans & Modeling Room Improvements

[DevGods_YT]

Hello. I would like to strictly in the modeling room (because I know the sculpt room would take a massive overhaul to implement) have Non destructive booleans. Im not sure about the memory footprint of 3d coat and how heavy it is currently but I did have an idea for implementing this. It would require new features added to the poly groups. Right now the only option you have for poly groups when right clicking is to change the color reference. You also cant parent poly groups. 

The ideal workflow though should be similar to zbrush where it automatically creates a new "Subtool" for you whenever you want to add more geometry. I know there is a boolean feature when using the primitive tools but this should be something that has to be triggered by the user. For me when I'm blocking out I like to add shapes quickly and I dont want to have to deal with them creating their own booleans by default anyways when I hit the apply button I would rather have something similar to every other program where booleans are something you must explicitly turn on. I do want new geometry to automatically add itself to a new poly group. Now this will require some added functionality written into the polygroups. Something similar to how the sculpt tree works in sculpt mode where you can ctrl or shift drag a layer on top of another to activate a boolean. 

What I think would be even cooler is if you could make a polygroup a child of another polygroup layer and have right click options on the child layer to set it to "Union, Subtractive, Intersect" This way the parent geo would know that its child is affecting it in a specific way and could render properly based on that. In theory this should allow users to move these children using the transform tools and have an update be triggered on the parent. 
I should also add that there should be by default no booleans when parenting on only toggled on by a right click menu. This way you could easily merge object together but still keep them housed in there own groups. 

I wonder if this is possible to try and implement with the scripting api's.