checksequenceverify – Does OP_CSV often trigger the timelock to be greater than the required time?

OP_CSV require that the transaction spending this UTXO could have nSequence equal or higher 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 less than 20 blocks, and now I need to spend this UTXO, I need to set the nSequence to twenty blocks, so ultimately the timelock can be 120 blocks.

Is it right?

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