It's not a simple case of reading data from the raw though. Out of those you listed, yes, white balance can be trivially read from the metadata and applied to t

It's not a simple case of reading data from the raw though. Out of those you listed, yes, white balance can be trivially read from the metadata and applied to the processing automatically, and in fact DT does do exactly that. "Color space", by which I assume you mean input color profile aka the color matrix of the camera's sensor, has to be calibrated or reverse engineered by shooting standardized color targets under standard illuminants. DT does have this data and applies it automatically, but the calibration is provided by users and might not be ideal. You would probably get better results by doing your own calibration, but that is somewhat involved. Picture control things like saturation etc that you select in camera are post processing steps that the camera applies to the raw in order to get a "developed" jpeg. They are proprietary to the camera maker and not published. Even if you can read settings like "saturation" and "portrait mode" from the metadata, you don't know which algorithm exactly that implies. Lightroom and other commercial software works with camera makers under NDA in order to reproduce the camera's processing. Could it be reverse engineered by open source software? Maybe, but the DT devs decided that they prefer to go in another direction.