Checking the Spark results, I found that ProtocalLib has a higher than normal EventLoopProxy value.

https://spark.lucko.me/f4NMV3P3RY

As said like a billion times on the issue tracker, this is not a ProtocolLib related thing. As you can see in the sources tab ProtocolLib uses only a small proportion of the actual processing which is normal as the packet events need to get published before writing them: