any use case ?

The idea came up by the wish to have a visual overview about which database is configured to be used as master or slave of an application instance.
Think of having always two application servers that may be configured to use one database as master and another database as slave out of three databases.

Now when having lots of application instances one has to maintain dedicated maps.
In this simple example are six links with 12 triggers = no fun
one (application) host had to be removed. so 3 links with 6 triggers = still no fun

Initially exporting the map, making lots of copies, updating the copies according instance and finally importing the new maps works. But as soon as something needs to be adjusted it doesn't help much.

thanks, but what exactly could be implemented to improve it ?

A host screen allows to be build once on template level and may consist of elements available on that level.
This host screen is then available for every to the respective template linked host.
For the template based elements the corresponding host level elements are used.

Host maps could provide the same for map elements.

Admittedly this is probably of little benefit to most people.

ok, got the idea. would work best for people that use host to describe a more complex system where it makes sense to visualise them individually.