You can already export tiddlers as plain text (rendered or not) to get things like .cpp files or script files out of them using the exporter. For a contract I did a while ago I made a wiki that would automatically generate code and there were buttons to export the generated files so people could make changes without having to know how to code. I have a similar wiki now that documents and generates some components for robbie. Once I finish testing I am probably going to make it public.
The widget can export any type of file that is registered by the core to be encoded in base64 when imported into a tiddlywiki. The list of files registered this way is ['image/gif', 'image/x-icon', 'image/jpeg', 'image/jpeg', 'image/png', 'image/svg+xml', 'application/pdf', 'application/zip', 'application/font-woff', 'application/x-font-ttf', 'audio/ogg', 'video/mp4', 'audio/mp3', 'audio/mp4'].
I have only tested exporting images so far.
You could make a button that exports a tiddler using the existing export mechanism. Or you could have it export a list of them, but you would be prompted to download them one at a time. You could probably make something using the jszip plugin to download a zip file that contains everything to get a single download. But that isn't really part of the downloadBinary widget.