We have rolled out charybdis 3.3 on the network with server-side MLOCK enforcement. What this means is that instead of ChanServ reverting changes in it's MLOCK, the modechanges are simply not accepted to begin with. For example, doing /mode #opers -t yields the following:
15:29:56 [staticbox] >> Server: #opers t inst MODE cannot be set due to channel having an active MLOCK restriction policy
Please let us know if you have any questions by joining #help or #staticbox and have a nice winter.