No problem at all - the SetiQueue program takes very little cpu power to run. I run such a SetiQueue at home for my "fleet" of machines, and I run an instance of the SETI client on each of the CPUs(dual-config) as well.
I simply gave the machine that is the SetiQueue "server" a static IP and run the queue - in my case, it's a private IP: 192.168.1.40:5517 Then on the regular SETI clients running on each CPU, I simply use the -proxy command to point them to the SetiQueue(as above) and that's it.
I don't happen to use SetiDriver on any of my PCs, but it's still fairly easy to setup. 🙂