It's not much of a concern because if the event loop processes
1. a bunch of DT mutations (which schedule the restripe) in one turn
2. a bunch more DT mutations in another turn somehow inserted before the restripe task
3. the restripe task

The inserted step 2 would still only update the start index of the restripe task. It would actually save work, since what would normally happen would be that 1 would be followed by its scheduled restripe, then what is numbered as 2 above would be followed by another restripe that it scheduled.

There is a potential breakage here, though, and that's if `table.destroy()` is called before the restripe task. So the code inside the `setTimeout` should check for null pointers before using the nodes. Maybe checking `!self.get('destroyed') && self.tbodyNode && self.tbodyNode.inDoc()`