No problem.
My approach with the configs is just to work with ocio env vars that we set in Nuke or RV from the SG ocio fields.
We tend to populate the look and lut fields during ingest (hiero_export hooks) using Nuke Studio. I’ve also gone so far as to publish any cdl, cubes used on the NS timeline.
The config.ocio becomes almost generic enough for most projects. The only major headache at the moment is the fact you can’t define colorspaceTransform in and out profiles via environment variables, so these still need hard-coded on a per-project basis. That being said, I think Nuke 12 is using a more up-to-date compile of OCIO which is supposed to support env vars for those values… I just haven’t had a chance to test it yet.