I read it, I even tried that solution. I tried both using the "-c" option passing a custom .opt file to that, that overwrote my custom .opt file putting all .cfg file options in there for some reason, then I tried using per content directory override, which saves again a file with the entries from .cfg files, not the entries from the .opt file.
If what you mean is that there's a way to change the default opt file for that core, and save it as a per content directory override, I still have to try it, but for sure it's not what was suggested in this thread.