I understand this is tradeoff but the infrastructure changes are not as frequent and they seems to have higher risk of breaking some less common pipelines. There are at least two examples:

1. our stress and enterprise test scenario pipelines are getting broken on regular cadence as they do not run on most changes
2. updates to test matrix - update alpine test images #81841 was green and then eventually fixed by Revert "update alpine test images" #82309. In this case, coreclr tests use library tests, but they do not run test changes.

Since the PR pipelines runs are selective based on the modified files, it is really difficult to make sure clan CI when updating test images or doing infra changes. We may certainly also do only for subset e.g. eng/pipelines/