Hello and welcome to the forum 🙂
It depends what you mean by a "view". A list or chart is technically a view and they have different display options and variations that can show or work with data in different ways.
You can use backend functions to get data and supply values to input fields on a form to filter other fields with (like lists) - we do this with apps like Tickets
that uses a backend function to execute the global search to populate an input field to filter a results list. (Check the global search form in the Tickets
app for an example)
But ultimately, you are limited by what our field types can display. I don´t think we can handle a dynamically sized tree structure (e. g. with unlimited depth) well with our current list fields.