Not sure if I should try rather suggest this directly to your T4 team, but to provide completely reusable "best-practice" code-samples you could use this way of using standard T4 referred in the T4 blog:
I am the person behind that methodology, but I wanted to refer you through the T4 team's blog, because it's really just basic T4 usage in a certain way.
This way any code sample you currently produce could be turned an independent automation filling up that certain role. Some blocks of course fit in this role better than others (and some not at all), but most of the "reference implementation + guidance"
comes crystal clear and reusable when abstract-automated.
Let me know, if you're interested to hear more. I'll be happy to explain.