<snip>
No, they are not the same. What you have linked as explanation on learnmeabitcoin.com is a transaction with a locktime in the future. If it is already signed you can only broadcast it when the locktime has elapsed. If you try to broadcast it before the locktime is elapsed, every receiving node will reject and drop your transaction. It can't and won't be mined into a block because that would make the block invalid if it contains a transaction with a locktime still in the future.
If you're the only holder of such a signed transaction, you could delete the transaction and create a new one. The Bitcoin network obviously doesn't know about your locktime-transaction as you can't broadcast it upfront.
What is described in this thread is a P2SH transaction that has a redeem script that can only be fulfilled when the locktime in the redeem script has elapsed. Before that, any attempt to transfer funds locked by such a redeem script will fail. All funds locked by such an address are truely locked until the script's locktime has elapsed. You can't do anything about it, unless you change the code of every participating node in the Bitcoin network (not gonna happen).
Public addresses are nothing more than recipes how to redeem funds which "have been sent to" such addresses. The expression "sent to a public address" is technically incorrect. What you express by that is to specify a certain type of redeem script and how to fulfill it to be able to move the locked coins by that redeem script. The Bitcoin blockchain itself doesn't know anything about public addresses, nor does it contain them.
A time-locked redeem script gives a P2SH address of the form 3..., the hash of the redeem script is the public address.
There was recently a thread where someone sent a substantial amount of Bitcoin to a P2SH address where the redeem script can only be fulfilled in 125 years (likely due to a 0 digit too much when the redeem script was constructed). Well, shit happens...
