With so much uncertainty I would down scope to:
a. Users can specify a default entity view to show for a db view entry point
b. Users can select a entity view and that becomes their preferred entity view (but a. overrides b.)
Then just beta test this and observe usage and response before fully committing to the final implementation.
I tend to agree that per-view setting will be useful.
Not all views will be relevant for the user. Since some of the views are never relevant if you look at the context (example: when you never write content about a subject, then the view with content items is never relevant).
So I think it will be confusing for users.
Also on these kind of views it’s not that UI friendly to switch between views as shown in the demo video.
The following is not based on the price, but purely the difference between ‘basic’ and ‘pro’.
It feels odd that such a common problem (having too many information on a page) can be only solved when you have a Pro account 
I can understand that if you only want to show views to certain people with certain roles that it’s logic that you need a Pro account.
But isn’t it a bit odd that if a user purely wants ‘tabs’ to avoid information overkill that they need the most expensive version to achieve that?
First release of Multiple Entity Views is here
Kinda have to agree here – I think that multiple views solves so many problems for new users (Fibery can be a bit overwhelming at first), that it’s a bit of a shame to have it only on Pro plans.