You can't hack Treadmarks in that way, since the game is a dictatorship when the server and only the server can determine position, speed, hit and miss, number of rounds left, firing time of a weapons, etc. Which means that a server op can easily overload the server with the wrong or bad mods, as the server is handling all the book-keeping for the clients.
Something that can happen is that one of the mod has a flaw, in which the server can't determine who "owns" the projectile that registered a frag. Usually it ends up being credited to 'The World', but there are certain ents that will cause the game to think the last player mentioned by the game (being fragged, fragging, alt-k-ing, joining whatever) "owned" the projectile.
Most Ents inherit ownership, but some ents don't and using these ents in a particular way with weapons will cause this issue.
An example or an overwhelmed server: in the original version of my Armageddon server, I was using a beta of a SSO weapon I created which, when a player was fragged by this weapon, the game registered the player as being fragged multiple times by different AIs. The weapon was causing too many spawned ents, and eventually led to memory corruption when the server was up for a few days leading into this problem.