Using the built-in join operator, there's not much support for any of the points you've raised. The internal state cannot be inspected, nor can you do an ad-hoc query against those tables.
As for side outputs, what you can sometimes do is to create a statement set that includes both the primary query and a secondary query with the opposite condition. The Flink SQL planner will co-optimize the two queries, having them share as much as possible of the early stages of both pipelines, and then fork the data streams as needed to produce different outputs. Depending on the details, this may or may not be a useful technique.
A possible alternative would be to use a PTF instead of the built-in join(s). A single ProcessTableFunction can have 12 input tables, and since you'd be managing all the state yourself, you could make it inspectable or queryable.