You would grab the most current gtimes.ids via Near Infinity (in the OVERRIDE or the ids folder depending on your settings).
But, I think I know what happened for you, and it's not good. IEP Banter Accelerator deinstalls any already installed Banter Accelerator. And by doing so, weidu has to deinstall - and reinstall - all mods that were installed in between.
The DEBUG throws a lot of errors, e.g.:
Unable to Unlink [keto\Backup/2/MOVE.2]: Unix.Unix_error(20, "unlink", "keto\\Backup/2/MOVE.2")
Which is not a good sign but could be ok in the end. But then it says:
[iepbanters/scripts/baldur.baf] PARSE ERROR at line 7 column 16-74
Near Text: )
[RealSetGlobalTimer] argument [I#BANTER_TIMER] not found in [GTimes.IDS]
What probably happened? Well... first IEP Banters patched the gtimes.ids with the I#BANTER_TIMER entry.
Then it told weidu to uninstall any older banter accelerator. Uninstalling all the mods in between lead to weidu restoring the files from the backups of the mods that were installed in between - with the old gtimes.ids inside because apparently, one of the other mods changed it, too. Which doesn't contain an entry for I#BANTER_TIMER.
It installed all other mods again - still no new entry for I#BANTER_TIMER, because IEP banters thinks it already did this.
Then it tries to compile the additional scripts, not finding an entry for I#BANTER_TIMER, giving an error and setting to to "0".
Ouch.
Is this for the install with the weidu.log you attached here? Because I don't see iepbanters even in there. I would have expected to find it with a "INSTALLED WITH WARNINGS".
For your case I can only offer you a quick fix.
Deinstall the Stutter Debug Tool.
Open Baldur.bcs with Near Infinity.
Replace any line you see with
RealSetGlobalTimer("I#BanterTimer","GLOBAL",0)
with:
RealSetGlobalTimer("I#BanterTimer","GLOBAL",2700)
Klick the "compile" button, then save the baldur.bcs.
This should fix the stutter because now the timer will actually run.