Problem:
The user was unable to choose the dynamic source for an Image block inside of a content template.

Solution:
We have a known issue similar to this one that happens especially for a content template that has advanced conditions, for example, conditions on taxonomies.

As a workaround, create a new content template and assign it only to the custom post type. Then, create the block inside of it and you will be able to choose the image. After that, make that block reusable, and you can reuse it in your current content template.

Problem:
The user asks if Toolset enqueue scripts and styles to the frontend. He is trying to optimize the loading speed of the site.

Solution:
Yes, Toolset views/blocks and forms will load some styles and scripts to the frontend. The latest release of Views/Blocks has implemented an optimization technique that lazy loads the scripts and styles using Javascript. This behavior can be disabled using a constant in wp-config.php file. Check it on this previous ticket

https://toolset.com/forums/topic/enqueue-wordpress-child-theme-css-files-after-toolset-blocks-style-css/

That way, you can dequeue Toolset files when they are not needed.

Problem:
The user was having issues with the block editor when he uses a different permalink structure than the plain one.

Solution:
The blocks editor depend on the REST API, and the REST API depends on the mod_rewrite mode of the server. The user was able to fix the nginx configuration to fix the issue. Check this reply https://toolset.com/forums/topic/gutenberg-issues-related-to-permalinks-structure/#post-2110407