Well sure, the library source code is available - you could implement your own virtual Phidgets. This would be pretty difficult to do well without a lot of insider info about how the library works.
I'm surprised that there hasn't more interest in this over the years (judging by these forums), just the odd query that seemed to relate.
Maybe an easy-ish alternative would be a public server which has a number of Phidgets connected, and to which one could connect?
At least for input-only devices, there might not be any contention problem. And perhaps for outputs, users could be rationed by a queuing system or some such.
Is this something you might consider providing, if more folk were interested?
in the past, with python my teams have used the mock library to achieve the required behaviors without hardware attached.
i'm currently integrating phidgets in a .NET project; if you'd provide interfaces for each of the concrete classes, we could achieve the same using github dot com /devlooped/moq (not posting external links is incredibly lame wtf)
this might be a helpful interim step that has very little dev cost to your team. currently i'm having to generate the interfaces and wrappers myself which is tedious but straightforward - it would be nice if we could remove that clutter from our repo, but it's necessary for us to include your products in our continuous integration testing.