The Timelock contract is typically not inherited by an ERC20 contract. Usually its deployed by itself and then used in conjunction with a multisig contract or a DOA. The OpenZeppelin Governor example shows how to use it pretty well.
So, you would:
Deploy the Timelock contract by itself.
Deploy your multisig/DOA/Governor contract
Make the multisig/DOA/Governor have both the proposer role and executor role in the Timelock.
Have the account that deployed the contract renounce its TIMELOCK_ADMIN_ROLE role in the Timelock.
Multisig/Doa/Governor queues tasks and then executes tasks from the Timelock.
Technically, you certainly could use the timelock as a parent class of your ERC20, that's just not a common pattern I've seen before.