I'm just going to assume this is a bug and post my solution. Independant confirmation would still be nice, though, so please comment.

1. Open 'SD.Feeder.TechnicianIncidentForms' project
2. Open 'Create Incident' web form component
3. Open 'Save As Template' sub dialog component
4. Go to user interaction tab and edit the forms model
5. Open the 'Create Template Object' single value mapping component and edit the mapping definition
6. Right click on the line extending from EnsembleSecurityToken.Email (on the left) to CreatedBy (on the right) and select Convert->Convert to ProcessMappingAssignment
7. Double click that same line and edit the conversion model.
8. Drop a 'True False Rule' component in the dialog and another 'End' component. Name them whatever you want, but for this I'm calling the rule component 'User Only?' and the two ends 'System' and 'Email'.
9. Set the True Fale Rule to use the variable 'UserOnlyTemplate'.
10. Connect the false outcome to the 'System' end component and set that component to create value with a data value of 'System'.
11. Connect the true outcome to the 'Email' end component and set that component to value from data pointing to EnsembleSecurityToken.Email.
12. Click okay back through the nearly dozen sub dialog boxes you have open and then save and publish the workflow.

Also, this solution does bring up some interesting questions for me. First, does this mean that all users can delete or modify this template? The only permission I see that would relate to this is the control over the Submit Incident (Advanced) form (Service.Items.AdvancedIncident), so I guess as long as you trust someone to access that form you must also trust them to not mess up the templates. Second, assuming I'm right about the first, would the best solution be to add a column to the template table that determines whether or not a template is global while keeping the 'CreatedBy' column as a way to track who did create a template and possibly limit editing to the original creator?