Weird, never had any of those issues. I've always had state near the top and used props to bring it down. Pure components (which is any function component) do not re-render unless their props change. I've built rather complex applications also in the logistics and financial forecasting verticals. We are talking many tables, charts, dashboards, etc...
In fact, I found the MobX approach with reactivity harder to control performance for because it's triggered by state changes. But when you trigger a lot of state updates it can be really hard to reason about performance because it's not obvious what components will update due to that change in state.
Tables, Charts and Dashboards sounds like a lot of displaying of data. Not updating state. Or when you are updating state (like date picker), you're updating the world. Just an assumption, sorry if I'm wrong. Web is usually fine to be honest, doesn't come up until you're pushing state on keypress. The Stripe onboarding page and Twitter create tweet UI both have these performance problems. My day to day is React Native which is where these problems crop up almost immediately and getting performance out of the box is a chore that, again, none of the other frameworks make you do. Computers are smart they can solve these problems for us.
In fact, I found the MobX approach with reactivity harder to control performance for because it's triggered by state changes. But when you trigger a lot of state updates it can be really hard to reason about performance because it's not obvious what components will update due to that change in state.