Well, I caon only partially agree to this view. Perhaps if you would provide some konledge base with enough CSS code examples and allow users to pick samples and work with this it would be some kind of workaround but this is not available and me (myself as new user of this product) am completely lost and confused.
Especially when even simple things like naming the Page Body Text --- (just) "text" so new user has no idea what it applies to.
Why you are wrong about the complexity ?
Simply because I have used THEMLER and ARTISTEER for many years and none of the things you mentioned was an issue adding complexity (to the developers of that software), despite I already used DOM technology. Those products were god until J4. They for some reson quit development (at least for now).
Perhaps we got spoiled with those tools but I was able to setup 99,9% of everything visually and that cut down site development time by 70%. That is huge time saver. While SPB/Template is kinda time saver is it not as convenient.
Adding some extra classes does not build complexity, but would allow much better organization (instead so much of an inheritance).
I also use another tools doe PHP development which uses CSS and it has build in CSS editor where everything is done visually, which makes things ten times faster. Of course you can do everything in code but here we are interested in delivering the products no learning to code CSS/PHP/JS etc.
When someone is not familiar with the Joomla CSS , then you SPB CSS structure then he will be completely lost. PAsting pieces of code without understanding why/what for etc does not really help. IT is just a temporary work-around, where user will trip over next issues again and again and as a result will bother you - the support guys, then in turn you would waste huge amount of time dealing with each user separately.
One thing positive I can say about SPB team is that at least we (users) do not have to wait forever for replies (like it happens with the other products) and this has great value. That is the reason I haven't requested a refund, despite I am a bit dissatisfied with the Helix.
I tried Gantry template once and it wasn't to bad, but there was almost no Technical Support, so this was the reason I will never use it again.
Perhaps if you could provide more CSS documentation it would help. Also if you so oriented into CSS embeded into the template , then the template should provide much more places to inject that code. At the moment there are only 3 CSS hooks , which is rather a shame...
I would also like to see some setting to completely separate the template CSS from PAGE/Article CSS. This way user could setup pages without worying that they get affected (READ: messed up) by even small changes in template settings (which at the moment happened to me several times). This is absolutely unacceptable.
Finally I have to say this:
Other support members) provided me at least 4-5 times CSS code to embeed and so far not even one sample worked :-(