Additionally, the technology behind BPF changed significantly in the last years to the point where the original meaning (Berkeley Packet Filter) doesn't really have anything to do with BPF anymore. BPF is not limited to network sockets anymore (or something else associated with Berkeley), it is not limited to packets anymore and filtering is not the only use case anymore. The reason that the BPF acronym stuck all those years is that the new BPF features were introduced gradually, there was no particular kernel release introducing a BPF version 2 with all the new features (a release which could have been used for changing the name).

In theory, the kernel people could come up with a new acronym (something like Kernel Bytecode Language might be appropriate), but at this point it's probably too late.