I don't exactly understand what you mean by 'it can give different results'.
At the moment you can filter a view based on the data in the entities in the collection the view is a view of.
This should be extended to a filter mechanism which let you filter a view based on data related to that data in the entities in the collection the view is a view of, and I think that's doable, and should give the results you expect, as it works with in-memory data ONLY. So if you fetch a hierarchy, you should be able to get a view of a collection in that hierarchy based on a filter which filters on related data. For example: you fetch customers and orders. It should be possible to filter the customer view based on a filter on orders.
It's perhaps a hard thing to program, I'm not sure, I haven't looked into the gory details yet. The main thing is that it should be unwinded from leaf to root, using simple set logic: first filter the orders, then see if that set offers any results, yes then mark that predicate as true in the whole equation of predicates. If the whole set of predicates resolves to true for that customer, the customer is accepted.