Because many (some would say most) use cases don't have an actual window in their critical section where
- The invariant the Mutex protects is broken.
- There is a possibility of a panic.
Usually that's simply not the case. You only need poisoning if you have the mutex unlocked and you are temporarily breaking its invariant before reconstructing the invariant and there's a possibility of panic before that reconstruction occurs.
Even if your use case is like that, there's a fairly good argument that mutex.lock() should just automatically panic and should not require mutex.lock().unwrap(), because most applications would never try to handle a poisoning error. They would just propogate the panic and try to shut down ASAP. If you really wanted to handle that poison, we could just have a different method for that, like mutex.try_poison_lock() or whatever. But the standard library unfortunately chose that mutex.lock() should return a poison error.