That article is arguably about fighting Javascript for performance of a global store.
If a language is designed to favor a global store for app state, it is feasible to compute paths at compile-time, and even link paths to the final layout of state.
It would be useful to model state as a set of second-class implicit parameters, subject to structured translations for hierarchical components, instead of first-class values.
We might express fine-grained state notifications in terms of coroutines that yield via 'await Condition', or alternatively via incremental computation of repetitive transactions. In any case, a compiler could play a role here, too.
Anyhow, performance problems cannot be blamed solely on a software architecture, especially not when implementation involves working around the language instead of with it.