I haven't used it, but I think threads::lite does just that, spawn a mostly separate interpreter with a fresh (OS) thread. It also sets up some communication channels between the main thread and the new thread, but it shares nothing.

Judging from the caveats in the documentation, loaded modules stay loaded, but all local namespacess with imports seem to be wiped. So it's not a completely clean interpreter but roughly equivalent.