How do you reduce e2e test maintenance at scale?

Teams with 200+ cypress tests start spending more time maintaining them than writing new features. Every frontend PR that touches components means someone has to go update selectors in the test suite, re record fixtures, re run to check for new flakes and then debug the three tests that mysteriously started failing for reasons completely unrelated to the PR. How is this sustainable? The maintenance cost scales linearly with test count and I haven't seen anyone mention that when the decision is made to "invest in testing quality". Has anyone figured a decent workaround?