When you're at a point of tuning Tokio, consider taking a look at ef_vi/DPDK + SPDK

One great use of agentic coding is being able to add and very granular tracing instrumentation to help with these sort of optimizations.

All of the significant server applications I have encountered in the industry have suffered from the same problem, which surprised their authors but seemed obvious to me: the application was spending the majority of its CPU time doing meta-work like entering and leaving epoll, stealing work from itself, etc. There are principles for writing Tokio servers and these are good points in the OP but I think they are little-known and too easy to violate.