the code posted in your wiki page link is tagged as "proof-of-concept".
Yes, because in its current form it's not useful at all. A real solution would be to create something useful out of it. If I wasn't clear enough: you can have the EXIF, you can have the JPEG, you can do anything with the file name. All you need is to find and intercept the Open() and possibly the Write() and Close() call(s) in that task.
The possibilities are:
- prevent writing to the card AND transfer the jpeg image over USB,
- modify the EXIF before writing,
- modify the file name / file path (if that would make any sense)
But this is a bit off-topic. For messing with the file name itself, it's not worth the trouble
