I suggest an additional type of template parameter that is a specialized version of the string-type parameter, for the primary purpose of allowing the templates to accept drag-and-drop from tags and immediately interpret them as their tag path. It would then also allow UDTs to interactive more natively with Indirect Tags, which has all manner of positive side-effects (repeaters, canvases, etc).
Fundamentally it should be the same as a string-type parameter, but with the addition of allowing interactions with the template to prioritize using the tag path rather than other aspects of the tag.
For instance if you drag and drop a UDT onto the template that has a path-type parameter flagged as the Drop Target, it will fill the field with the path of the UDT rather than a UDT-type parameter that would latch onto the UDT itself.