In our project, some Configuration instances represent references to the top of the project and are applied by convention plugin to all project modules. When building the dependency graph, the AffectedModuleDetector treats these references as dependencies, resulting in every project module being considered "affected" by all others.
Having the ability to filter configurations would allow us to specifically manage this scenario, restoring the proper function of the AffectedModuleDetector.