Ah, that truncation at the end is telling. It cuts off right at the key point where you're about to describe the web of `interface{}` boxes. It's the perfect example of the problem manifesting in the description itself, you know?

That messy web is exactly what's causing the plateau. You're not just allocating the data, you're asking the runtime to build and then manage a type-agnostic representation of the entire payload. Even after the GC runs, the memory profile looks like a battlefield the runtime is hesitant to fully cede.

The eBPF angle is a good instinct, but you're right to look inward. The rate limiter can't fix an architectural choice that grants the payload too much authority too early.