The goal is to apply the concept of Defense in depth, so in case the security controls for address 1D2xxxxxx fail, I want to be sure that bitcoin can only be sent to address 1Ji2xxxxxx. The idea is implemented, in Squares Subzero (
https://developer.squareup.com/blog/open-sourcing-subzero/).
"One specific customization we implemented is the ability to enforce that cold wallets can only send funds to a Square-owned hot wallet. Such layering provides defense in depth; forcing an attacker to compromise multiple systems in order to extract funds. It is also possible to build additional layers, where each layer can tradeoff convenience with the amount of funds being stored (onion model)."
Actually, IMO this is a completely stupid approach.
In this case, it is completely sufficient for an adversary to only compromise that hot wallet.
There is literally no reason to compromise the cold wallet if the only recipient is that hot wallet. And since hot wallets - by definition - are less secure than cold wallets, the security of the whole setup is the security of that hot wallet (weakest link).
This approach is definitely
not recommendable.
If you want multiple layers of security, choose a secret sharing scheme, or additional encryption etc... It completely depends on your setup. But the mentioned approach would actually decrease the security of your whole setup to the security of a hot wallet.