Your are right, the dng file are generated by raw2dng (developed by Alex) that's inside the raw2dng.app package so this is something that need to be solved there, the know issue are relative to the GUI wrapper that do the work of starting the command line tool for the raw dragged in.
Added it to first topic
I think alex is already working on it. I can't test that problem because don't know Resolve and all those raw video procedures with proxies and so on.
What is the basic raw video workflow?
RAW to DNG
folder that should be cinemaDNG
Editing software
I saw that there is a win batch converted that converts to tiff and makes proxy but didn't get why or what they are.
Scrax, here is the workflow that I do with the Black Magic Cinema Camera that records in 12-bit Raw Cinema DNG (which work the same with the 5D Raw if you can transform raw to DNG DNG cinema..) :
When you open Da Vinci Resolve It recognizes Cinema DNG because I think in the first DNG file, there is the content of the metadata Cinema (Time Code, Frame Rate, T-Stop, Reel Name, Camera Label) + photo metadata record.
Then we created proxies to ProRes 422, which only contain the metadata cinema to edit the footage on any professional NLE (Premiere, FCP X, Avid, etc..).
Once finished editing, you export the project in XML and conformation is due to metadata Cinema, to link to the DNG. From there, Resolve recognizes files and keeps the edit right.
We can then do the color grading in raw.
If DNG is converted to Tiff is no longer raw.