Yes, you absolutely can have ‘hybrid’ approaches to a certain extent—but they’re still not the same.
A good (and popular) example of this is Notion. They have a folder-hierarchy based system at the core, and you’re also able to have properties on pages in a database and cross-reference those pages onto other pages (connect them). Additionally, you can have ‘synced blocks’ that pull reference data across different pages. This feels considerably more ‘connected’ as a system than Google Docs. However, this is still a fundamentally tree-hierarchy system. If you delete a page that has another page nested inside it, the ‘children’ will also be deleted.
Anytype (and other object-based systems) don’t have a location at all for their objects. We can emulate structure through views, categories, queries, etc. (like Collections 2.0) but the system principles on a technical level are fundamentally different. Structure is emergent, not imposed by ‘where an object is created’ like it is in tree hierarchy systems. We cannot suddenly implement location for objects, file paths, etc. in the traditional sense on top of this object based system. If you delete an object that has another object linked inside it, the linked object will still exist.
Anyway, I digress. This is a much larger topic that has many online materials on. 