General question: Block Themes, Custom Post Types, Meta-Box-Blocks, Custom Query Blocks, and ACF

Hi! This is more of a general issue - ACF and block themes.

It is my understanding that in block themes every dynamic query has to be encapsulated in blocks ("glorified shortcodes" as the core principles page calls them ;)).

In Block themes, on the output side we will needs a block that encapsulates what is currently a template part with a custom field query.

But on the input side? I'm not sure how long Post/type Metaboxes will be supported in the current format, yet I don't see how the need for post-level meta/data could possibly disappear, as post/types will still be the smallest data container that can be queried. Actually, it's the most common use case in every single project I've worked on. Yet WP/Gutenberg/Block Themes - despite many advantages - is making this most common use case quite a bit more complex to realize than in the current Custom Post Type as data container/ACF/Custom query paradigm.

WRT to block themes and this use case - currently ACF-blocks (as far as I know) cannot save to post/type meta which would in turn allow them to act as meta-boxes for a post/type. They also don't support exposure of custom field values to the rest-api which would allow the blocks on the output side to use them in a query.

Currently, such a block-meta-box can only be created using native block controls - as, eg, detailed in this post
https://wholesomecode.ltd/guides/custom-meta-boxes-wordpress-gutenberg/ . Yet there is no complete overlap of components with ACF (for backward compatibility, for example) and functionality of complex field types.

So I guess my question is - will there be a way to use ACF blocks/fieldsets as "metabox-block" on a post/type in the future?
Will there be components for more complex ACF field types to be used when creating custom native meta-box blocks?

Again - I don't see how the need for post-level meta/data could possibly disappear, as post/types will still be the smallest data container that can be queried. So if fse/block themes is where the ecosystem is headed, this functionality will have to be somehow replicated in the new paradigm (posibly with the added benefit of having a form with a preview button in the editor).

Which makes me wonder what ACF's strategy in this respect may be? Butmaybe my current understanding of how this specific problem could be addressed is missing something important? So thanks for any comment.

No repository files or tests are named. Start by reviewing the ACF blocks, custom post type/meta-box, block theme, and REST API concerns in the issue and its linked custom meta-box guide; done would be a clear answer about support or plans for using ACF fieldsets as post/type meta-boxes and exposing their values.