I'm having similar thoughts with similar history as you.
I just looked at the Centos 7 EOL for maintenance updates, it's June 2024. I've been running on Centos 7 for what, 5 years now? And have quite a bit going on with certain configs, not 100% of course all done through WHM but probably 90% of it. SysAdmin isn't my primary skill but I have 20 years experience doing 90% of the work myself. I cringe at the thought of how many things are going to break by trying to do an in-place upgrade to Centos 8 then AlmaLinux (I've got all sorts of PHP scripts using all sorts of packages, Python using Selenium+Chromedriver, Configserver Firewall, yada yada) Yes, theoretically they should all come over but any SysAdmin with a lot of history knows these things virtually never go smoothly. Since I'm running on like a 5-year old (or more) config, it's probably wiser to do a fresh AlmaLinux install, migrate all the WHM/Cpanel stuff as much as Cpanel will allow and then see how much more work I have to do. It may take longer but seems like a lot of 'junk' could be left behind from an in place upgrade to Centos 8 then to AlmaLinux.
I'm holding out until if and when Cpanel introduces their own migration utility to get from Centos 7.9 to AlmaLinux. Maybe never going to happen? My gut is telling me to just hire an expert Sysadmin/DevOps Specialist to just migrate to a fresh install of the O/S, brief them on everything going on, on the server. Create a test checklist. They can then ,odify the local LMHOST mapping for the domains to map the domains to the new server just for the local machine and test. That way if it turns into a nightmare we can continue to hang on to Centos 7.9 while we troubleshoot all the issues.
Not looking forward to this but probably wise to do it by EOL of Centos 7 even though I'm not running anything that needs high-security (storing financial info, etc.)