Couldn't agree more and something I have raised before.
Some of our Lineage maps are very large and whilst some only contain 5 to 10 "Hops", the hierarchy of Systems, Deployed Apps, Servers, Databases, Schema, Tables, Columns and View underneath those systems cause the diagrams to render very slowly even though the user only wanted to see which system a file went to and didnt care about the specific table it was ETL'd to.
Allowing more types of filters (including relationship types (not just predicates)) and allowing an admin to set the default diagram type (Lineage / Impact / Process) and a saved view for each Asset type (set at an enterprise wide level) would be a simple and elegant solution to the problem