So, I cheated and jumped out of MT, and decided to use server side includes instead (which I already use throughout the Gamegrene.com site). Now, I use the following bit of code to dynamically create an SSI instruction keyed to the category name. Then, I have various files named after the categories which contain just the bit of individualistic template text I need.
CODE
<!--#include virtual="../mt_templates/category_<$MTEntryCategory dirify="1"$>.info" -->
This is a lot more scaling than the other alternative I presented above (as it really only requires adding a new "category_CATEGORYNAME.info" file for each new category you create).
Hey, works for me! Probably the best (easiest?) way to duplicate this within MT would be to double decode the $MT$ tags (so that one could embed an $MT$ tag within an $MT$ tag itself. This, however, is a pretty rare feature that anyone would use. Perhaps the better suggestion would be to make *every* MT tag parsable within any context/archive. If the user shoots themselves in the foot, than so be it. But for people like me, I could have used that bit of hackery within MT, as opposed to jumping into another tech (SSI, in this case).