Virtualizing for concurrent isolation

John Haller wrote, on 2012-09-27:

virtualization in a stable, reliable form is something I'd like to look into including at some point.
https://portableapps.com/news/2012-09-27--portableapps.com-platform-11.0...

Does this mean that the PortableApps.com platform only migrates changes upon app termination?

For those unfamiliar with these terms, there are two common methods of portablizing an app that isn't already portable: one is by virtualizing its system access (intercepting registry and file changes and redirecting them to a portable folder); the other is by allowing changes on the host and then migrating them into the portable folder when the app terminates, according to a pre-packaged knowledge base about what regions that particular app is known to change or by monitoring it while it runs.

I would prefer to use PortableApps instead of JauntePE ("JPE"), to gain the benefits of its launcher menu, update frequency, and broad community support. But I'm very timid about losing the protections I've enjoyed with JPE for many years. It truly leaves no trace* on the host system, even during app operation, nor even if power is lost or the whole machine crashes. Furthermore, registry conflicts are impossible between apps with JPE, which allows me to run them all concurrently without "fighting" over ownership of file types, DLL handlers, etc.

Does PortableApps already offer the protections I crave, perhaps using methods I'm not aware of? If not, consider this another +1 vote for adopting virtualization tech, someday sooner rather than later.

*No trace specific to that app, anyway. I'm not bothered by changes Windows itself makes in response to an app, such as recording exe signatures or tracking usage of hardware peripherals.