When a site builder creates a content type it is highly likely that they will want an entity reference view for that type.
For example if I create a type "Address" I almost certainly want to reference that type in "location" or "Event". Similarly if I create a type "Song" I almost certainly want to reference that with a multi-value reference field in "Album". When you think about it the mere fact that I am creating a "type" ie. an entity of which there will be more than one, implies that at some point I will want to show a list of those things.
The only cases I can think of where an entity would not require a view are ones where core has already provided a view (content, files, recent content, recent comments etc.).
When a site builder creates a content type they should see a "View settings" tab in the vertical tabs with the option "Create an entity reference view" checked by default, and the descriptive text: "With an entity reference view you can attach content of one type to content of another type. For example a type "song" with an entity reference view could be attached to a type "Album" by adding an entity reference field."