A usecase would be: A “Events” page should only have the event type templates to choose
from e.g. “event-concert”, “event-lection”, “event-jamsession”.
So, if a new template/event type is created e.g. “event-exhibition” i have also modify the "Events"
blueprint as well.
For me is that no problem, because I as the developer will control, which blueprint is posible where.
If I would follow your idea, the names of the blueprints are restricted by the other blueprints, which may be on an older websire are in use in other parts of the website. I sometimes reuse an old blueprint at a new position in the sitemenu too.