Some comments according to the limited experience i have on CMI myself.
I believe that what you ask is pretty much logical, due to the fact that local dev envs usually end up being different than the actual remote Dev instance. Testing modules, code, configuration e.t.c is pretty much the reason for that.
This makes default CMI functionality unusable as you dont want to move the whole configuration into your actual deployment process (DEV->IGR->PROD).
This problem is addressed quite well using Features, however it could also be tackled by some CMI related modules such as Config partial export or Configuration Split
One more argument in favour of Features might be that you are able to have totally different local dev envs than the remote Dev (Dest site UUID != Source site UUID) which i guess would make CMI unusable.