There are multiple ways you can configure GodsEye to make cleaning hackers from your server more efficient, this can be done by designing special configs, here are some configs that I have personally designed (I didn't invent the idea, just designed the idea into GodsEye)

Ghost configuration

The idea of the ghost configuration is to make GodsEye completely invisible to the players, that means that any features of GodsEye that affect gameplay need to be disabled, in the checks.yml file these settings are called cancel/canceling, means canceling the illegal activities that happened

The advantage of disabling this setting is that the cheater can never know if his cheat is bypassing or not until he gets banned, and when he gets banned it's too late, this even sometimes makes the cheater increase his settings meaning fly faster, run faster, use more reach, increase the cps on his AutoClicker which makes GodsEye detect him even faster and eventually ban him faster

Stability of that tactic

If you are going to make this kind of config, this means that in cases of false positives the player will get more violations then falses with the cancel on, my recommendation is to pretty much use double of the violations you hade set before for movement checks, and a third more for combat

Pros and Cons

The advantage of using that method is that you are going to ban way more hackers and ban them fast and it will be very very hard to know which settings are bypassing and which don't especially if you enable ban waves and make them ban once a day or once a week. The drawback of using this however is that you basically disable all of GodsEye's cheat prevention systems and basically let the players freely cheat and have an advantage in games until GodsEye decides to ban them

Moderation based configuration

This kind of configuration heavily relies on your moderation team, unless you have got a very big and dedicated moderation team you shouldn't use this tactic, this tactic is meant to allow for 0% false positives because the one that is actually going to ban the player is your staff team, for this tactic you want to disable kicking and banning for all of the checks in the checks.yml file, then you want to disable all of the settings called to cancel for all of the checks (the cancel setting is explain more in the ghost config above), by allowing the players to use cheats and not prevent the cheats it would be way easier to actually see the players hacking, flying, running super fast, etc... and the player will get way more flags,

your staff will see the flags and quick teleport vanished to the player to actually see him hacking, in a few seconds your staff will verify that the player is hacking and will ban him,

this tactic is good because uses human verification in addition to GodsEye's collected data, the downside of this is that you depend on your staff actually being online which let's face it, don't always happen

This tactic basically makes GodsEye become your advanced alerting system, and like any other has its own advantages and disadvantages