This is the original WCS as built by KM the higher version number you've been discussing is an offshoot development, Unless Mind (who I don't know) is around & still has the source, it won't be fixable. I could only look at the version for which I had source & even then needed pointing to the right place & telling what to change.
@ Sarah the high banwith usage is a function of the attack, not a bug, lots of massively oversize primary packets, plus floods of list requests which the server responds to in order to be answering the real ones, & bandwith usage inevitably rises in proportion to the level of attack it's under. I'd venture to suggest something similar would be observed in any server that stays connected & listing under these conditions, It's just obvious with WCS, as the usage is right there in the server console. Most other chatservers I've used would require you to run separate tools to determine this.
Setting it in dialup mode would reduce usage by making fewer primary connections, but I wouldn't recommend it, as listing your room becomes erratic even under normal conditions, but it might be worth trying for any host where the bandwith used is a big issue.