It seems to me that you are thinking of "distributing" QF, that is, a framework that would be able to work across processes and even perhaps across different networked machines. This obviously goes beyond the current QF capabilities.
Before you start re-implementing the while QF API, I'd recommend using the Proxy design pattern (see the GoF book). Obviously, you would need to explicitly code proxies on both ends of the cross-process communication, but the rest of the application could be mostly unaware of the "distributed" nature of the application.
I believe that on Windows, you could compile QF (and also QEP) to a DLL, and thus you could easily share the QP code among many processes. (As opposed to statically linking each process with a separate copy of the QP code.)