Sorry for being late to the conversation but you guys have pointed out a hole in TW that View Templates simply cannot fulfill. In short, View Templates do not get applied when Transclusion is used to insert a tiddler within another tiddler.
As an example, I have a public wiki designed for players and GMs of Dungeons & Dragons that is designed to be expanded upon by each D&D player who downloads it and customizes it for their own use. Like your roles and cards, things in D&D are grouped into categories or types. Such as in-game-world stuff like Monsters, Spells, Abilities, NPCs, Equipment, and so on.
Typically, an tiddler in each category is displayed in a specific way. For example, a Monster like a Skeleton (see link for how monsters are rendered) is always displayed with its combat statistics rather than as a normal tiddler that contains text. And a Spell like Fireball is always displayed another way. The first solution everyone would point to is “create a View Template for each category”.
The issue is with View Templates is they only work when the Skeleton tiddler is opened within the Story River. There are many times when I want to transclude a Skeleton within another tiddler. In my first version of this wiki where I used View Templates, I cannot simply just transclude using {{Skeleton}} or {{Fireball}} and have the tiddler be displayed correctly. I have to specify which View Template to use {{Skeleton||$:/dnd/templates/Monster}} or leverage macros like tabs that allow me to specify a template to display multiple monsters. This complicates the life for new users of my D&D Wiki who wants to simply transclude a monster, spell, NPC into their tiddlers.
Thus in my current version of the D&D Wiki, I designed it so it is possible to simply transclude {{Skeleton}} and have it show up with all its stats formatted properly. It however makes it harder for me, because I have to do the work for them in every monster tiddler. Basically, the text field of every monster tiddler is a hard coded transclusion with a template. This also has the side effect of having to move everything that is supposed to be in the standard text field to another field (for me, I use the content field).