CAD/CAM software with Cartesian planes are already confusing as is for most folks. Once I started watching some videos discussing tolerances and such from an engineer perspective, the layout, tooling and concepts made a lot more sense to me.
At that point, it's essentially understanding the intention of the tools and if you're performing additive manufacturing or subtractive. A lot of CAD/CAM software is geared toward machine shops and setups and mindsets like that and not necessarily 3D printer-esque communities. I think these solutions are great for the 3D crowd and not so much the engineer.
There are some in-between things that break the mold and do things in unique ways for people who are product designers like Rhino. The node editing in that is so cool. I look forward to seeing what more people can do with AI now and scripting.
I'm reminded of the concept of "ejecting" from e.g. Create React App a few years back - the idea was that if your beginner-friendly interface is actually built on the same underlying engine (in this case bundler and deployment assumptions) you can have full fidelity when you need customization, albeit with a one-way transition.
In the JS world things moved more towards build systems where beginner-friendly-DX and full-configurability could coexist. I'm not sure that CAD has the same dynamic.
Perhaps something like nested layers could work: you can use a complex model as a layer, but only opaquely, and build things around it with solids-and-holes; you can then lift that to itself a complex model, do things with professional CAD, and then treat the result itself as an opaque complex model if you switch back? That gets complicated fast.
Why can't we have both ?