checksequenceverify – Does OP_CSV normally trigger the timelock to be greater than the desired time?

OP_CSV require that the transaction spending this UTXO could have nSequence equal or better that the worth within the OP_CSV.

So if the UTXO with the OP_CSV created 100 blocks in the past, and set the relative timelock for under 20 blocks, and now I need to spend this UTXO, I need to set the nSequence to twenty blocks, so finally the timelock will probably be 120 blocks.

Is it appropriate?

If sure, it implies that more often than not the relative timelock is greater than the worth set, until you spent the UTXO within the very subsequent block after it was created.