I've seen an odd distribution of Interrupts like that before and it doesn't indicate a problem. I suspect the Linux OS has allocated these processors to handle hardware interrupts (hi% in top output) from the NICs and other devices, which are separate from soft interrupts (si% in top - SoftIRQ among others) that are processed only by SND cores.
Yes the number of RX-DRPs on your Mgmt interface is too high, because Multi-Queue is not allowed on the defined management interface in R80.40; there is no way to enable it on the Mgmt interface other than to move your management interface out of the way. I recently ran into this and just posted this update to the Max Power 2020 addendum thread:
p. 221: If possible, do not set an R80.40's firewall’s management interface to a NIC that is carrying a heavy amount of production traffic to avoid possible frame loss (RX-DRP as shown by command netstat -ni) caused by the lack of Multi-Queue on that interface. If the management interface has been changed from a busy production interface and Multi-Queue is still not active on that busy interface (use the expert mode mq_mng –o –vv command to check this) see this SK: sk167200: Multi-queue state is "off" when changing the management interface. It appears that the restriction blocking the activation Multi-Queue on the firewall's management interface has been lifted in R81.
Don't worry about the low Accelerated Conns percentage, it just means that connection rule matches are not being cached/templated by SecureXL. Many blades can cause this effect including Anti-bot.
Gaia 4.18 (R82) Immersion Tips, Tricks, & Best Practices
Self-Guided Video Series Coming Soon