>The simplest is to only handle things you can really handle at the current frame and let everything else filter to the top and interrupt entire process.

I find this approach creates exactly what you try to avoid: error handling complexity.

The problem is with the Exceptions I believe. They mess with normal program flow. They create code that's hard to reason about, that's less explicit.

Sometimes Exceptions can clean up some code, but usually it just sweeps dirt under the carpet to blow up in your face later.

I rather use sum types and actual return statements (or implicit returns when all code is expressions) than Exceptions.