In my case, I just don't want to have to do multiple touches of some of our sites gateways. That is, they are not clustered and any upgrade is then an outage to that site while it is performed. I'd rather get to 80.20 in one step as opposed to multiple steps over a period of time. Also, it appears that using CPUSE to upgrade to 80.20 is not a viable way to get the new filesystem, so it likely would be another fresh install if we deem any benefit from the new filesystem. I'm not opposed to fresh installs since they can be performed rather quickly these days, I just don't like taking outages.
I can always plan our management server upgrade/install at a more appropriate time. One of the reasons I feel the need to stay at 80.10 there is because we use a separate log server located in Azure, and Checkpoint recommends (or states) that the versions should be the same. As there is no approved upgrade path for our Azure log server we are stuck at 80.10 there.