@ejacobson it really is tricky to find a sweetspot. For me it comes to checking things at different levels. If you are doing some e2e / journey tests, then you (probably) only really care about completing that journey successfully. All those other assertions you mention are probably better tested elsewhere.
If that e2e tests fails it should fail because something is wrong with that key journey. Not because of a typo on page 2.
I’ve had good success with breaking suites into different categories and running them in order of importance. e.g. e2e flows, pages look ok tests, etc
If the e2e tests pass then you can run the next batch and so on. You get quicker feedback on the stuff you care about most. And don’t lose anything in terms of coverage.
Alternative approaches are worth considering.