Here lies the problem. We want to avoid creating a unique template for each item. If the item is not a matrix item, this is easy as getcurrent works well and allows a single template to be used on many items as long as they are not matrix items. However, when we have matrix items, getcurrent can not be used because some info is stored in a field in the child item. So instead of getcurrentattribute, we have to use getattribute, which means each parent item has to have a unique template. If there was a way to mass update item templates, we might consider "one template per parent item" a scalable solution. We really need a way to source child item info from its parent. When we create a custom field at the parent level that includes a getattribute tag calling a field in one of it's children, it breaks. Ideally, every parent matrix item should have a custom tab that sources every field in each of it's children, thus getcurrentattribute would work.
In summary, here are 3 possible solutions that would help.
1. Allow getattribute tags to work in custom fields (custom parent field sourcing it's child items)
2. Mass update templates
3. Templating System with editable regions, etc so most of the template can be mass updated.