I still can't see the point of titleblock templates at all.
What's the benefit ? Title blocks are not your typical everyday's job,
quite the opposite, it's something you create/modify pretty rarely, so
what's to be gained in automating something you do once in a blue moon ?
Automation is required when you do something complex, title blocks are
very simple, and something whose details can be much better addressed manually.
And when title blocks change how do you address that with templates ?
It seems there isn't any "automation" for this, you have to concoct something
yourself with journals and the likes to chase all the drawings around, a hellish
job which is at best a large waste of time (if you ever manage to catch them all).
Compared to this, what you mention as the "bad points" of patterns makes me smile,
I have done these several times and took me nothing in terms of time, and even
less in terms of complication, these are simple, straightforward operations.
And, yes, patterns DO reference attributes beautifully, once imported they read
them and they appear there read-only, which is perfect, so why should we mess up
things using TB templates ? Is it just for the sake of using a brand new command
instead of using the "old" patterns ? At Siemens there is clearly the need for
fancy new commands to be featured on brochures, but as engineers we should be
intelligent enough to choose what really works, not what is fashionable.