I think you bring excellent points, and I agree with your desire to make it more useful.
I’m just realistic that such massive improvement would take a development team probably 3-5X of what McNeel has now, and will only be useful for people doing Industrial design type of work. Even though I would welcome that (that’s what we do), I think Rhino could go out of business pleasing us. It’s a lousy/demanding(no pun intended by me saying this)/small market to be in.
It makes more sense to play extremely well with MCAD packages first. For example, I cannot open a Step/Parasolid Assembly change a hard to model thing in Rhino and export it back out maintaining its structure/assemblies/naming/colors intact. I want that waaaaay before I want them to build a draft-angles/fillets/shelling/Boolean Division for Chuck to have an army of typists.
Blocks are overdue and they would help everyone. Including McNeel because we could all work with much smaller files if those things were half useful.
Also working really well with world class rendering plugins like Octane and Vray should be a much higher priority than any pet projects in rendering. Same goes for a seamless integration/livelink with Blender/Zbrush/Unreal/etc.
My thinking: Let’s pick battles where we can all win.
I’m happy to pass on shelled parts of money-making designs to Fusion, Solidworks, our clients’ engineering teams or some offshore supplier.