In your case you are using that type of timer in the wrong place.
Timers do NOT need to be started in the setup() it is just that that is the best place to start interval timers that run from then on.
But as you discovered, a setTimeout() timer is a one shot deal. If you want to run it again, your simply use the same command again, wherever it is most useful in your code.
However, as far as possible bugs go in both SimpleTmer and BlynkTimer, I have noticed that when using Timer ID’s and associated ID based commands (most notably deleteTimer() in my experiments) that it will completely stop the first timer called in your code… apparently never to work again?? To “solve” this, I simply create a first sacrificial timeout timer that does nothing…