Mark said:
Ideally, a template should just be a template and load only pure css / js or if there is a need to cache the css / js a compressor. That should just be it Perhaps Joomla should figure out on the "framework" part because if Joomla includes a template framework of its own, none of this issue would happen
A thought for you to consider 'down the line' when you have all your products integrated on one platform (or possibly as a parallel project so it does not interfere with core business):
Stackideas is not a template provider but can add value to the core business and also expand brand awareness by producing 1 non-framework template (call it Stackideas) based on (for example) Protostar and optimised for SEO, load speed, layout and interaction of all your products.
It becomes your 'in house' showpiece template for all your products but the 'Stackideas template' (as it would be called) could also be sold as another product within your portfolio.
The mix of template/component/modules/plugins allows great flexibility in developing the business in whatever direction you wish to take it, but selling the Stackideas template allows you keep the brand name in view even if none of your other products are used by whoever purchases it.
You could also give the template away as a marketing cost/promotion to increase brand awareness because if people use your Stackideas template they are probably going to come back to you looking for some software to use on it.
If you base it on the Joomla core it also make it different (not another framework), faster and does not directly compete with other members of the Joomla template community.
Anyway, just something for you to consider for the future, obviously continue to do whatever you feel is the right path to take for what is already a top quality business.