The Firebolt team clarified two things. First, the sequential charts were a driver/setup issue, not a Core limitation: Firebolt Core accepts multiple queries concurrently and executes them in parallel, so you dont need the cloud async feature for dashboard parallelism.
Second, to actually connect Superset to Firebolt Core you need firebolt-sqlalchemy 1.1.0+, which added Core support. Use a connection string like:
firebolt://{database}?url={url}
Point url at your Firebolt Core container's address and port. The reporter got it fully working on Superset 4.1.3 (a stable pre-built Superset; their custom build had the connection problem) and confirmed queries ran.
Source: https://github.com/firebolt-db/firebolt-core/issues/12