JS: setInterval has weird behavior with chrome throttling

Question

I was testing my website out with chrome throttling, using the low-end mobile. I noticed one of my JS intervals were running much slower than it should be for no reason. I decided to investigate further, so I wrote this code:

let prev = Date.now();
let x = 0;
setInterval(() => {
  if(x++ % 100 == 0) {
    console.log(Date.now() - prev);
    prev = Date.now();
  }
}, 10);

It sets an interval to run every 10ms, and it prints the time elapsed every 100 runs. This should be 1 second, but it is printing 4-8 seconds. This shouldn't happen, because getting the date every 100 runs, and then logging it, should be a piece of cake, even for "low-end mobile".

My best guess right now is that chrome's throttling also specifically throttles the event loop, which sometimes gives misleading results, like here. Is this true?