A time to live on Application Components and Messages possible?

[Longhouse81]

The concept:
BOT sends a message (Message Components, Empheral etc) with a TTL option in it, discord register itself based on the TTL when this message or component etc gets deleted and handles this itself by internal CRON.

Example:
BOT sends a message with some buttons, the bot registers internal these buttons will work for the determined TTL.
Up to this point, there is not that much more transfer than adding some TTL to the API request what is minimal in size.
What differs is what happens next, the BOT needs to resend the message without the buttons and upon receiving it Discord has to determine if there are any changes in the content and then conclude the buttons are deleted and edit the message.

Discussion:
I'm not going to speak out by any means i know how the Discord servers operate in the background!
The general question is if it's worth that 2nd API call when you know upfront as BOT you want to delete certain parts or delete the whole message. I know for a fact on the BOT side it's using more resources and bandwidth...

• a TTL in the message for general deletion or in it's subparts like component row or embed

Is this viable for life, would it use more resources on the Discord side?