There were some examples given earlier in this thread where it was ‘convenient’ to have entries in a template of the type that could trigger an error at run time.
I agree fixing the templates is a tidier solution, but as there appear to be lots of frequently used containers whose default templates could trigger this error then the old behaviour was made available as a stop-gap to cut down on the number of people (incorrectly) reporting docker as broken after updating Unraid. There is nothing stopping you from NOT installing the plugin and fixing the templates for any containers you use that then fail.