Recognizing this use case is a bit odd (And TBH I think harder than using the socket to communicate with a daemon)...
I'm, not sure how I feel about making that kind of change. It's a change in something akin to an API, so there are lots of drawbacks. And as it's not entirely a use case I think is common, it's not what I'd optimize for.
That said, you have at least one clever workaround. You can embed some kind of query identifier in your query directly. eg: something like:
osqueryd -S --json "select 'time' as _query, * from time; select 'osquery_info' as _query, * from osquery_info"