If you truly use it a lot, buy a second hub while they’re on sale. Cloud requests are going to use a lot of the hub’s time, no way around that. If you haven’t already, change the event history and state history to 1 on your echo devices. That will make your database much smaller, which may also help.
@rlithgow1 hit the nail on the head - the table makes it easier to see if there are any z-wave issues. Your topology indicates that your mesh needs some strengthening (red is bad, blue is good). I don't think my mesh is particularly good, and it has a lot more blue that yours does.
I thought this was happening a couple years ago and put ES on SmartThings until last August or September when I moved it back to HE. I think a combination of improvements with HE and ES software have contributed to my not seeing any issues with it since. That said, I only have about 15 pretty simple rules that use ES and only 9 of my Echos integrated with HE.
Keep in mind that the more battery powered devices you have the more you will see red in general. Red blocks by its nature doesn't exactly mean you have problems, but you have more chance for not having enough routes for devices to get to the hub reliably. More blue is always better, but allot of battery powered devices will lead to allot of red as well.
I purchased a second hub a while ago and find it very useful to be able to have some “problematic” devices on a separate hub. This includes non-standard Zigbee devices, resource intensive devices and also, since one is a C-7 and the other (second hub) is a C-5, Z-Wave devices that play better with the 500 series chip.
The Hub Mesh functionality works extremely well at making all devices available to the desired hub.
I would certainly recommend purchasing a second hub while it is on sale.