This will require new ERC/ENSIP? or updating erc3668 to retry after 4xx error & bad data:…?
or it’s used as wrapper like current universal resolve with it’s own ccip proxy?
We couldn’t even update erc5559 (@ 
Stagnant | Standards Track ERC) which is only used/tested by few… erc7700 is in draft & we are fully redesigning current draft to cover all future chain-agnostic/cross chain storage providers as our current draft was more focused on 5599/3668 type only.
~in short we can wrap erc3668/5599 selector in 7700 revert to use fail safe mode like CCIPReadRunner logic. We can even add full paranoid mode client requesting all ccip gateways and crosschecking results… or as recursive multisig CCIP calls? 
Still bigger concern on CCIP side is centralization & privacy risks… it’s well known issue as I rem reading long posts from ?Nick & Ricmoo few yrs back… 2nd huge issue, current records are signed by gateways, it should be signed by owner or using owner’s permits.
I’ve seen similar issues in old universal resolver, it was reading revert data’s length 0x0000…20 =32 as address. * it’s already fixed in new version…
we lost count of our small bugs reports found during deep diving. 
that was ~critical bug in old official universal resolver as all ccip checks pass & addr data is returned… BUT ETH/tokens sent to reverting sub/domain.eth would end up in 0x0000…20 address, but back then nobody was into deep universal/wildcard with callback&fallback mode.