Seems to describe something analogous instruction level parallelism, which traditional CPUs made this millennium have as well via instruction pipelines, branch prediction, and speculative execution. Some of which turned out to not work too well so now we generally run hobbled CPUs with Spectre/Meltdown mitigation enabled.
The reason why we tend to reach for difficult abstractions for core level parallelism is that most automatic/safe approaches tend to stumble pretty hard on Amdahl's law, where most parallel code is consequently almost entirely designed around minimizing critical sections.
I don't fully see how inets would resolve Amdahl's law.
So there is 'no sharing of state' baked into the computational model by design, enforced by this very simple and elegant design choice.