If you had a firewall in your network, for example, that had both a firewall system that you configured, and alongside it, a firewall configured by a third party with "best practices" in mind, that would be frustrating to configure and test because you'd never know for sure if it was a configuration you didn't setup correctly, or if it was this other firewall that you couldn't operate interfering with whatever it was you were doing.
When designing things like this, step 1 is you remove variables that could change the behavior of the device in question without you knowing why it did. I'm sure once completed, a self driving car system could well be made to interface with the safety systems otherwise present, or could be designed in such a way where they wouldn't conflict. When you're in the thick of building that system, however, an additional (and by your comment, not exactly predictable) system to contend with, that you have no access to, is going to be a pain in the rear.
Again, the stock auto break systems rarely engage unless there is real danger. By that I mean last second breaking, absolute last second. Most people can drive a lifetime without ever having them engaged. If you cant program a self driving car that can handle that then you're in the wrong business.
It should not be too hard to make these systems co-exist. If one of the systems says break then the car will break. The few times the car breaks when it really didn't need to should be an acceptable side-effect during testing.