reyalp
Note, I added add_ptp_handler to sig_ref_vxworks_1.txt, seems to be a good match.
Gives good match (though <100%) and finds the function correctly here, too (Ixus950): NSTUB(add_ptp_handler, 0xFF9EC59C).
So, if findsig can be trained to find add_ptp_handler() on (all) other cameras, I don't see any obstacle to including the basic PTP handling stuff to the autobuild right away.
There remains the mode switching stuff, for which I'd hard-code the "logical events" PressRecButton/PressPBButton -- if I read Microfunguy correctly, this works on most (all) cameras that he supports. It may not work correctly with PTP (e.g., may disconnect), but shouldn't crash the camera.
Then, I'd bundle mweerden's ptpcam as a basic PC-side client (ewavr's extensions require much more attention for each camera and computer).
Such minimal implementation, together with reyalp's Lua additions (levents, call by name/address, etc.), already gives a powerful interface.
It may be useful to make PTP extensions run-time-optional, although it is not obvious how to do that neatly (PTP handler registration happens in a task that is not synchronized with reading of config).
EDIT: Almost forgot... Merry Christmas! Und guten Rutsch, etc.!