Interesting work, but my initial reaction is this should not be added to CHDK.
In most cases, I expect if someone goes to the UI to delete, it means they really want to delete it. If they don't, then they should just rename it. So they should think before deleting, not depend on a trash function. I have never seen complaints from a user who accidentally deleted stuff with the file browsers, nor can I remember doing it myself. In that scenario, there are still FAT undelete utilities which should work pretty well if you act quickly.
A trash function which isn't entirely reliable would also be worse than none at all IMO.
The Canon UI doesn't include any undelete functionality, I don't think we need to be more idiot proof than the official UI.
If you want I can replace/modify the "remove" function so that all files which are deleted from CHDK come into trash.
This would be very bad, think scripts or raw ops that use temporary files.