Hope that gives you some ideas. If you have a specific use scenario you are interested in, then please let us know.
I was thinking of running some operations on the root filesystem by kexec-rebooting into an appliance to get exclusive access.
I promise to look at this in more detail when I'm back at work next week, but a quick question: where would the 'client' end of the connection (ie. libguestfs) be running in this scenario?
In kexec, everything would be local (LIBGUESTFS_BACKEND=direct or unix:). If blocks is reworked to integrate with guestfs, there might be several options depending if python is client-side or daemon side, but it doesn't make much difference for the kexec case.
I would like to do something like that for my blocks tool (which does conversions to LVM and bcache).