I think that's fair to say. And importantly, a "stress" is what keeps a user from achieving the utility of a product.

That's why I tried to break it down to component stresses as much as possible. A tap, a swipe, a single second of page load, a single second spent looking around for something that's hard to find each counting as a single "stress."

That said, there would have to be a ton of research done to see how equivalent these things really are on the whole. And of course it's going to be context dependent.

I meant this more as a framework for thinking about making user flows as simple as possible, and the implications on your product.