Generally speaking plugins can’t access values from grafana.ini unless explicitly passed to them by grafana core.
If the user sets under its configuration a [plugin.$pluginid] section it can be used to pass specific configuration to the plugin but this doesn’t work too well in Grafana cloud and you can probably achieve much better results via the configuration form of a plugin.
The [plugin.<pluginid>] in grafana.ini configuration does appear in the backend plugin environment variables, (but not passed to the backend plugin via PluginContext).
If you have a section in grafana.ini for your plugin:
This would be nice to add to the grafana.ini documentation.
I just tested that, grafana 11.5.3 (in development mode, i.e. docker compose up --build). The parallel access in the front-end seems to take more steps…