each individual case. Otherwise it's just another service that has 99% chance to sucker you up.
I wonder how that could work. Imagine he receives a wallet containing claimed 100 Bitcoins. He tries to open it, but can't. Then how can he get the escrow funds back? He can claim he deleted the wallet but still, it could be possible that he gets the escrow funds back and then suddenly the 100 bitcoins vanish from the wallet he claimed he couldn't bruteforce.
I would not accept such an escrow. Or at least make the risk clear to the one with the blocked wallet. If he understands and agrees that i can't be held responsible for that risk then i might do it.
Its also not the only way. For some wallets its possible to work on a private key that holds no funds to get the password. The password is the same for the entire wallet, but its useless without the encrypted private key that holds the 100 BTC. The change address you used 1 year ago and now has 10000 satoshi left is perfectly fine.
See e.g. the post by knightdk above.
Didn't realize that possibility. Thats a good way then. Unfortunately probably only for experinced users because newbies very rarely will have private keys being stored somewhere. But it might be a good advice for newbies to back up a private key of an unused or empty address when creating a wallet.
Experienced users probably will run rarely into that situation. Making backups is probably something experienced users already had to learn so a lost password might be rarely happening for them.