This would be lovely to have! Just like you can create as many views as needed to entities / types in the Smart Folders, adding a field for “Views” to add views that are not necessary directly related to the entity itself.
This would allow for (fake) “Lookup collections” that are just views filtered contextually without being read only (and other missing features the lookup collection view has).
Use case example:
Department → Projects → Tasks
If I want to see all the tasks in a board view (by assignee), the only way either make a view in a smart folder, or add another view to the “Projects” relation that will show the tasks. But this is a bit weird because the label for that relation is just “Projects”.
If we can add “View” fields to a database, then it will be able to show those views in the entity view. It would be less about the data or permissions within the view, and more about access to the view itself.
One difference is that (for some reason) in smart folders, and also in embeddable views, you can only select from the dropdown a database that is related (directly or indirectly) to the entity. But this would be nice to have that it does not need to be related. For example if I want to just see all open projects in a meeting. No need to have them related in any way, but have them in the meeting entity for us to have a look at for the meeting.
Embedding views into the rich text is not scaleable as it means it needs to be done for every department manually. And is then configurable by editors as opposed to only configures.