This 'second layer' would be jsons written to hive and managed largely by 3rd parties?

Is there a technical reason that precludes allowing hive to organically escrow a token created by locking hbd?

A gui would have to be created/incorporated into the existing front ends, but a base layer function that allows me to transfer the token/bond to another account through an escrow feature seems the most elegant way to me.
To have to introduce 3rd party risk would be a deal breaker outside the community being small enough that we can all know each other's reputation for trustworthiness.
Simply creating another H-E type arrangement doesn't solve the 3rd party risk issue, for me.
If there is a technical reason that is a bad idea please state that so I can better understand why we have waited this long for this feature.