It's slightly different, but in the past people thought about adding an option to bypass tables and have event subscribers send events directly through the logger. I don't think an agreement was reached on whether it fit osquery or not.
One thing that can be done here is to schedule a query using a 'discovery query':
https://osquery.readthedocs.io/en/stable/deployment/configuration/#discovery-queries
The discovery query would contain the event trigger (example:
SELECT * FROM process_events WHERE path = sudo
), and the body would contain the query you want to run in response to this event.