Custom CatalogStore vs PCV

[A-little-bit-of-data]

At present, it is observed that the interface https://trino.io/docs/474/admin/properties-catalog.html#catalog-management has a note:

Warning
This feature is experimental only. Because of the security implications the syntax might change and be backward incompatible.

Then I saw the document https://trino.io/docs/474/release/release-443.html with such an update
SPI
Add catalog store support for dynamic catalog storage implementation in connector plugins

Then I have a question. If I implement it myself based on this plugin, for example, persist the catalog to an external system such as S3, HDFS or MySQL to implement a dynamic catalog, is there any essential difference between this and the catalog-management function that is supported by itself but marked as experimental? Will the custom plugin that implements the dynamic catalog also have the same risks as this one marked as experimental?