So: descMetadata = the metadata for the template, and templateMetadata = the metadata for the object using said template.

This is certainly doable, but the cloning of a template onto a form currently relies on the simple, built-in attribute mapping magic that turns a fedora object into a form.  This is set up with a map which pulls data from descMetadata.

- We could hack the template cloning to dup the map and replace descMetadata with templateMetadata.  This is quick but certainly a hack, but it does ensure the ingest map and template map are essentially the same.
- We could build a new map just for translation of template metadata onto the form, but this risks template map and ingest map diverging.

I would prefer to get templates out of Fedora longer-term anyway.  Templates are a UI idea, not an archival object.  Having them act like real assets just makes for more exceptions as we build more code, plus if we ever want to map things onto the form that don't live in descMetadata (say workflow metadata for some reason), we have this same problem again.