In my oppinion argon is working well. During installation of their software they normally enable i2c using standard raspi-config commands. But osmc blocks those commands (which are standard at an raspi) and advises to use myOSMC. I do not think that that’s the job for any external script to detect modifications to standard scripts done by OSMC. raspi-config ist present as expected at a raspian system but the content is modified so that it does not work at all.
So in my opinion the problem is caused primary by OSMC. At a plain raspian system everythink works fine and without any need for manual changes by user.
There may be (or better I think there are) good reasons for OSMC to block raspi-config access. But in this case it would be a good option to enable an easy way to enable i2c within OSMC.
EDIT:
Sorry - I did not see your post at the second topic.
YES we should keep everything at one place. So lets stop here and keep Discussion - if any further discussion is required - there: