There is a hitreg problem I know about, but don't know how to fix. I was scolded by somebody on right here on the forums. They suggested just as I, to restart the server more often as after time the issue becomes worse. There is more diagnostics in source SDK. With my little knowledge I was trying to see if I could pinpoint the issue but the other guy raged at me to not do so even while I suggest to the server owners to restart more often. I gave up because of the scolding.
I have been a paidmin in the past and you must type status within x amount of time (maybe 30 seconds maybe 1 minute) by HG rules of reporting because as far as they are aware that was the only way to get steam id which is of course the only way to accurately ban people and avoid banning the wrong person with the same name or scams which fake the same name. There is actually a console command that will list all steam ids in a demo. That was in one of my other posts. I'm rather certain it was an OP, but it's worth the staff looking into, which can help ban hackers.
I don't really check up on this thread, and all I know about having different update rate and cmd rate (keep in mind everything works in ms not rates which always vary) If a dev wants more information as why to set cmd rate to 65 and update rate to 66 they should contact the creator of tf2's master comfig, yes that is with an M and yes you will have to hit the "i meant comfig not config" when searching on google. He has a discord. Funny thing is servers actually run 66.666... tick which is actually 15ms exactly per tick. 66 tick doesn't even line up with the server. 100 on 100 tick does though.