We really heavily on configuration management to install and configure Zabbix to our needs.
The default database that is shipped with Zabbix packages doesn't suite our needs as there are a lot of things in there that need to be deleted. For instance, we use a git repo with all of our templates that gets synced to Zabbix via the API through our config management tooling.
Leaving the default templates in place will make a mess of the Zabbix install.
Same goes for the default hosts ("Zabbix server") and the default actions, etc.
The way we currently work around this, is to have our config management drop the database after the initial deployment and import a custom database which is stripped of all of these things.
I think it would be beneficial for organisations using automated deployments to have the option to use a 'lightweight' version of the default database.