E.g. the developers who never ship code because they always want to write the better version of the thing, that they thought up while building the current version
At some point you have to look at a less than perfect design and answer the question of whether it's good enough for the requirements at hand.
It's not about striving for perfection.
It feels like the same coin to me: inability to accept calculated risk.
I'd look at this the other way around, there are people who don't strive for perfection, simply delivering something when it just meets expected bars, not giving any thought beyond that. I wouldn't want those people to design my safety systems, they'd just leave possible improvements lying on the ground by not caring to think a little beyond the boundary of their "box".
I work for a healthcare company, and we definitely put in charge of safety people who stress about a patient coming to harm, not people who are so-so about it.