Arduino-Libs VS TaskScheduler

There are some design decisions Arduino made that maybe restrict in one aspect, but there's nothing wrong with dropping down to a lower level or jumping sideways to a slightly customized version that does just the right thing. e.g. If digitalWrite() isn't fast enough, somebody wrote a digitalWriteFast() that works with some AVRs. Otherwise, you can probably just hunt down the source yourself, make your own copy of it, and change it to be the way you need. That's a great way to learn, too

When you get a little more advanced it's not hard to extend the BWD code to hsndle any number of "time when something should happen". Or you can use something like the TaskScheduler library.

Or just use TaskScheduler and never have to worry about this again. https://github.com/arkhipenko/TaskScheduler

For reference, I'm a big fan of this scheduler in particular, due to it's simplicity, OO support and a neat extra of sleeping each unused millisecond (low power for free).

One of my favourite low power techniques involves using a scheduller for your loop code, and sleep for 1 ms at a time when there are no tasks to run. As seen here.

Have you looked at the task scheduler library? https://github.com/arkhipenko/TaskScheduler