Dynamic current control on Wallbox Pulsar plus

[jostd]

I have started to use this ocpp integration to control my Wallbox Pulsar Plus chargers about a week ago.
I previously used the cloud API from Wallbox, but that is currently not workable with a multiple charger setup.
My main concern is that there are multiple means of limiting the charge current for dynamic (solar) charging, and I don't know which one I should use.

The oocp integration provides number._maximum_current, which sends a default profile to the charger. There are multiple instances on the web, where people warn, not to use default profiles, because it will wear out non-volatile memory on the charger. One discussion on this (ocpp) github page is here:
discussion 1566
One should rather use a (temporary) TxProfile in order to preserve non-volatile memory. I have tried this out and it works, But it is flying blind, as there is no HA entity/state associated with it. The service call (action) to ocpp.set_charge_rate with a custom profile doesn't appear to return a success state. I suppose one would have to retrieve the profile of that ID to check whether it stuck...

I have also read that the TxProfile being written to volatile memory is only a requirement for ocpp 2.0.1, not 1.6, which the wallbox chargers are running.

There are two additional methods for sending current limit to the integration:

1. The Pulsar Plus has a feature called chargingALimitConn1 which can be set and read via ocpp's configure and get_configuration commands. This also works to limit charging current
2. Occp also provides the limit_amps parameter for the set_char_rate command. I assume this one is accomplished via a profile, but I have not yet checked whether it is a default or temporary one.

Does anyone know what is best for the Wallbox chargers?