> eBPF runs code at the highest privilege level by actually extending the kernel

Yeah this was my thought when reading the above argument too.

Maybe they're thinking that in future, more and more kernel functionality will be moved to eBPF programs, and eBPF has a restricted execution environment? I can follow both lines of logic.