Yes. Simplest.
As I read it if the delay in the loop is longer than the debounce period of the buttons you are using, the library will be OK.
Or write something a bit more complicated and make the loop run at a fixed frequency, here use 50 Hz for example, giving the buttons 20 milliseconds of bouncing time. Code from blink without delay kinda thing.
It's a shame as that library seems to want to hit all the correct notes for doing the usual simple compact button debounce that just works.
It's almost like the author asked chatGPT to write it - plausible but on inspection srsly flawed.
ezButton doesn't suck, but curiously it doesn't like being serviced at less than some unknown frequency.
In a loop that runs free, it works well.
a7