Note that as a best practice, most of your rules should be logged.
The fact most of your rules are not logged is problematic for many reasons, including this specific exercise.
Regardless of whether you log a rule or not, every rule should log the number of hits against that rule.
It doesn't show by default in R80.x SmartConsole, but it's easy enough to see by right-clicking on the rule headers and ticking the box for hits:
If a rule has a low number of hits against it, that's a target for a rule that could potentially be removed.
In pre R80 releases for Check Point gateways, it was considered best practice to move rules that were hit a lot to the top of the rulebase to improve gateway performance.
With column-based matching added from R80.10, this is less needed, though there are still a few corner cases where it might help.
As far as potentially simplifying rulebase logic, that's something a tool or a human would have to address.
We also offer, via Check Point Professional Services, a service called SmartOptimize that can assist with this task as well.