I have a very similar use case as what you describe and would also rate this near the top of my list if not the very top. Right now you really need a separate view that is disconnected from the entity, or you have to use a smart folder, but this can’t always be used because of the limitations you can see I was fighting with here: JIRA Integration Causes Issues with Context Views.
It feels like Notion does this the most intuitive way with the properties and the canvas always being part of an entity. It feels like Coda and Fibery are kind of trying to appease the root needs of their users while specifically trying to avoid giving in to taking the approach Notion took. I think how Notion implemented this is probably its killer feature.
One other thing to mention is that in Coda, even though they don’t support embedding tables/views within a canvas/rich text field in the entity, you can at least convert a lookup field display into a table to achieve something like what you are wanting. For example, the screenshot below shows an example of a meeting entity that has a list of notes that are associated with a topic, which can be designated an action.
