That would turn communicating between threads into communicating between VMs, which is a disastrous change in itself.
It would. On the other hand multiprocessing with explicitly shared memory could be a fast (but potentially painful) workaround.
That could make sense for processes, which would also get around the exception unwind lock, but I don't know how that would work with every thread moved into a separate VM.
Of course. Using VMs here would very deep into overengineering territory.
how do you know the threads need to communicate with each other?
How do you know they don't?
If you want to avoid a global process lock, multiple processes will have less orchestration and communication overhead than multiple VMs (though still a lot more than necessary with threads within a process).