I will start work on a for-pay version of Clipfinder as soon as the beta phase for Clipfinder 2.2 is concluded. One of the features I am considering for this version is an alternative render engine.
As for the cake eating, I suggested to Jamie a 'plug-in' model, where we agree on a common interface and then each of us can develop, market and charge independently, but we could still offer users high integration between Jamie's work and mine.
To whet your appetite, this is what it currently looks like:
You order a plug-in from Jamie and install that into an "Extensions" folder. Clipfinder will then present JamFuze settings as part of its render settings
and execute Jamie's code for each rendered file.
So much for future plans.
I appreciate your feedback and comments, so please keep them coming.