Not being a modeler, my views will be strictly those of a potential customer.

Yes, poke-through is a problem. End of sentence.

Yes, as a consumer, I would prefer that YOU solve it.

That said...

For me it's like breast size on a female companion. Yes, I like them large, but it's by no means a deal breaker either way. If a garment is well designed and gives the character the characteristics that I want, yes, I'll work with poke through. After all, with the morph tool it's not that big a deal any more.

I would suggest that if the solution that you suggest to your customers is to make the body parts invisible (and yes, I do accept that as a solution under certain circumstances... read on...) then you better have the clothing designed so that you CAN make the parts that poke through invisible without it affecting the areas of the character skin that show through the cloth openings. This is especially important in skimpy slutware and in things like tee shirts, where part of the chest is going to show at the top of the neckline.

I would far, far, far, far rather have a male shirt with shoulder poke-through (solvable by making the shoulders invisible) than to have those god-awful cottom ball shoulder bumps that so many modelers include as the kludge to prevent said poke through. That's one where turning the shoulders invisible in the character would be the simple fix for me, instead of having to fiddle with the shape of the shoulders forever in the morph tool or in post work to fix the lousy design of the clothing.

Yes, including morphs in the clothing is another, probably preferable solution. It's one that I use on almost every piece I buy... I run them ALL through Morph Clothing and give them automorphing. For that reason, I pretty much don't care if the designer put any morphs in or not. It's all rock and roll to me. I suspect I'm in the minority in this area, so my realistic advice would be for you to at least include breast morphs in female clothing and muscle morphs in males. Again, I don't personally care.

For me the key is, Did you tell me about the pokethrough issues in the readme, and did you suggest how YOU deal with them as you use your own product. I'm really big into personal responsibility and owning what you do. If you tell me about it, and I agree that the solution makes sense, then it's my problem how well if works. If you keep it a secret, well... I'm going to want my money back.

Is any of this what you were looking for?