it won't help the problem is not unhanded request it is transactions that never finish
What do you mean? If your software makes a request that is not handled by any of thew real slaves, this default slave takes over and completes the transaction.
Of your are saying that your slave disappears right in the middle of the transaction? I don't think this bus is designed to handle this level of dynamic reconfiguration. I don't think any existing bus can do this. That's just stupid to expect that slave can disappear in the middle of the transaction.
if the slave disappears during a transaction or isn't there when a transaction is started the system
end up in a a dead lock. Once a master has set xVALID it must wait for xREADY
dynamic reconfiguration is entirely reasonable in a system with configurable logic.
A bus that crashes the whole system waiting forever on something that ought to take microseconds
is silly