Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Yeah, my suggestion is related to problem... when someone join the game and then join Lobby, then relog and login again, the command from commands.yml is executed (I have there kick command after 20s for sending to Lobby using movemenow, can't use option from config.yml, because there's missing delay and I have on my Auth server NPC to activate premium via fastlogin) and this player is then "freezed" and can't login and do anything.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Way to set delay when player is sent to another server using bungee: on in config and when setting there server, for ex. Lobby. Then way to set delay, then it teleports them for 20s after login.
bungeecord: true # Send player to this BungeeCord server after register/login sendPlayerTo: delay: 20 #new option, in ticks / seconds, it doesn't matter''
Here option: delay: Xs

So... Use there bungee command to send directly on server (BUT I can¨t use sending from configuration, cause I have on Auth server premium NPC to activate premium via FastLogin. Maybe if there was delay, when it will sends him, it would be ok.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Way to cancel actions from commands.yml, when player already isn't online on server (due to spam to console, that player is already offline and due to bugging with AuthmeBungee.

So... When players leaves server STOP counting delay of 400 ticks, so when he join again within these interval, it won't affect him?

Additional context
Add any other context or screenshots about the feature request here.
My current commands.yml example:

onLogin:
  lobby:
    command: 'kick %p Lobby'
    executor: CONSOLE
    delay: 400

But this bugs player when he log in, then leave server and he log in again to 20s... then he will be bugged when logging again, because he get kicked... way to cancel event will be good too. Or delay in default config.
SO....
Which kicks him into Lobby, but isn't so good solution, cause if he log in, then relog, and then don't authenticate till 20s, he's kicked again and everything is frozen for him (due to authme bungee, that he can't join servers as non authenticated, so he can't even use login now...).