You can achieve the isolation with jails and cgroups, but not the performance improvements.
And this is what I mean when I say that taken to its conclusion you're just reinventing processes.
I think this kind of performance claim needs to be solidly proven by something at least vaguely like a real running application to be taken as a given.
However, as Docker PaaS gains popularity, that may be a better alternative. Only benchmarks will tell :)
Shouldn't the unikernel approach actually improve reproducibility greatly? You build your application and all it's dependencies together, that should run exactly the same locally or on your Xen cloud.
An example of this is the Mirage website itself, where all the kernel outputs that are live are stored in GitHub at https://github.com/mirage/mirage-www-deployment -- an explanation of the Travis CI workflow is at http://www.openmirage.org/wiki/deploying-via-ci
If you want to bring the isolation level of that process down to just absolutely what it needs to run we've got things like jails and cgroups. You could probably run a Go app with no access to the filesystem since everything is linked in statically anyways.
I think it misses the reasons people are excited about virtualization. Reproducibility and uniformity of environment has a higher value than isolation to most software developers. The priorities may be inverted on the sysadmin side, but I don't think so far as to justify this kind of approach.