datetime.secondsUntil Technical/Performance Question

I’ve built what’s basically a customized a chess clock using Wappler and some custom JavaScript. I have run into browser throttling/performance issues when tabs are not visible and especially on mobile browsers. I just started exploring the Wappler datetime component and am wondering if it leverages setInterval under the hood, which I presume would be susceptible to similar throttling issues as my js solution. Is there a way to stop the interval calculation in a function like secondsUntil (ie stop the timer)? Has anyone run into performance/resource issues leverage the datetime.secondsUntil function? Any technical details of what’s behind the datetime component would be appreciated! Thanks!