That's only if you can (and do!) test everything locally. Otherwise, you are still beholden to the CI system.
It's a belt & suspenders approach - when you push a change, you want to have already tested it to a high degree of confidence because the feedback loop from CI back to the developer is too slow.
Effort spent moving all testing to the left supports faster iterations through shorter feedback loops. Creating stubs/mocks, HALs, etc. are all good investments.
Figure out you can easily clone the CI tasks and run them locally, and then build tools for developers to do that easily for every change :)
It took some redesign, but I was finally able to demonstrate how much could be done locally before pushes. Some just need their eyes opened up.