This readme file insists I ought to be able to enable and disable eBPF collector threads on the fly, but this commit ripped that function out citing requirements "from product team" and an "internal discussion."

Please explain what those requirements were, what that discussion was, and why your developer documentation still says I can (should! These collectors produce overhead!) do something you've specifically chosen to disallow.

Netdata has been promoting eBPF monitoring as though it's a fully-featured and production-ready solution since 2020 (putting a little "beta" symbol in the drawing doesn't count; your marketing and documentation copy use release vernacular), but it's still a transitional mess and the documentation does not match the current state of features. I'm simply trying to figure out which of the eBPF functions will actually work on my machine, with the agent, while it's running, and I don't need to keep editing its configuration file and restarting the thing to enable and disable its various threads. I ought to be able to do that with the API, but that "internal discussion" has been going on for almost a year.

You left all the machinery for thread manipulation in ebpf_functions.c alive and intact, but you removed the registering function call. Why? Why tell everyone this eBPF feature is release-ready when you haven't even finished sorting out which kernels each function can run on? This is silly. Why?