Two challenges with the current timelock-based operation

Thank you for offering the wonderful service of Defender. I particularly think it is great that non-engineers can perform the timelock operation.

However, I think there are two challenges with the current timelock-based operation.

  1. One is that if the timelock has the sole authority to upgrade the contract (in the case of multisig=>timelock=>target contract), it is not possible to upgrade the contract as described in the following tutorial without temporarily transferring authority to the multisig.

Ref.

  1. The second challenge is that the SDK does not support the pattern of using a timelock as an intermediary in the "create proposal" function (only supports multisig => target contract). If this is not supported, it is very painful to create a timelock-mediated proposal because manual work is required.

Ref

Please let me know if my understanding is incorrect.

I also read these material
(https://docs.openzeppelin.com/defender/admin#creating_timelocked_proposals)
(https://github.com/OpenZeppelin/defender-client/blob/master/packages/admin/src/models/proposal.ts#L19)