You know the old joke about a guy who goes to his doctor and says "it hurts when I do this" and the doctor responds "so, don't do that"?
Two examples of "so, don't do that" from Drupal are "Unable to add content to a content type named 'type'" (link) and "Do not require a 'title' field" (link).
I left comments at both links.
In the first case, my suggestion is to just don't have a content type named 'type'. You don't need that anyway. Just make it a compound word with some domain-specific word + 'type'. For instance, BookType or BuildingType. If someone gets the error at the first link, they'll ask on forums and, as long as they provide detailed information, someone will point out they shouldn't have called their type 'type'. There's no reason to add code for this, but it could be added to documentation.
In the second case, I think it's much easier to leave things as they are now. It's also much better for users and developers if everything has a title. IDs are required, and title should be too. Entities like a 'Person' node don't naturally have a title, but one can and should be provided for them even if just for administrative reasons. A 'Person' node might have 'First name' and 'Last name' fields, and those can be automatically combined using various modules or custom code. Listings of 'Person' nodes wouldn't have to be customized to use first/last name, they could use title as now. Think of the title not of the person, but of the 'Person' entity: a way for humans to quickly tell one 'Person' entity from another.