There is no caching and memory usage considerations when showing a specific configuration build history , is there? just trying to figure out the difference.
Its just that this filtered view you mentioned is the only real option to view all builds affecting a specific project - it is very convenient to view all the various configuration build history together as they tell the story of what was deployed using their common feature (project, which in our case indicates a deployment environment)
Basically I’m wishing for is a build “History” view for the filtered builds. (with the same columns as in a single build’s history view - including tags for example, or customized columns as discissdd here 
)