Initially I think it would be more like #1 -- osquery has access to other streams such as syslog, ASL, windows eventlog -- I wonder if it would be useful for osquery to be able to ship the Falco alerts into the same logging pipeline that folks already have set up. Additionally, if osquery is running on the container host, there are other tables that could have value.
#2 and #3 totally agreed it doesn't make much sense.
If I were to approach such a thing initially it might be an osquery extension in Go that just makes the Falco events available. I could also theoretically see Fleet being able to manage rules and that kinda thing, but it would be further down the line after proving out the idea that it's useful for logs generated by Falco to flow through that same logging pipeline.