Thanks @jurgenhaas for taking your time to read my issue and for your detailed response. I fully agree with your point that the models should be well documented and in the language of the business rather than using technical terms.
Just some background why this idea came up in the first place: we are introducing a new software product based on Drupal/ECA and a lot of the ECA process models are provided by the creators of this product. We are starting to create our own models now, and in the future we will have to maintain/alter some of the provided ECA processes. As some of the provided process models were less documented, we had to use the properties dialog a lot in order to understand how these processes work. And some of the provided models were documented in a more technical way. So the idea to use the metadata as a default (using some sort of expert/debug view mode of the model) came up.
But taking your experienced feedback into account, I think we were trying to solve the wrong problem with our idea. Establishing some form of styleguide/best practices/acceptance criteria for provided process models/modeling in general would certainly be more helpful in our scenario. If employees who create ECA process models strive to create well-documented models in the language of the business then it should not be necessary to use the selected template as the default in the name field because every Event/Flow/Action would get a proper name anyway (at least in an ideal world, naming is hard :-)).
I could still see some value in having an option to enable/disable a technical/expert view that would show the metadata in addition to the names/documentation in the business language (faster debugging without having to dig into properties dialogs, both the technical and the business view united in one view). But for me, as a (more or less) novice in terms of Drupal/ECA it is hard to tell whether this would benefit more experienced users so I leave it up to you to decide whether you want to close this issue or not.
In any case, your insights were really helpful and I appreciate the time and effort you have put into this and your very supportive attitute, so thank you very much!