How to avoid the need to run 'env default' command on modified env variable

[Mircea Carausu]

Hi All,
apologies in advance if my question is trivial:

I am changing some critical variables in the read-only / compiled-in
section of u-boot env variables via CFG_EXTRA_ENV_SETTINGS in
include/configs/<my_board.h>
All I want is to have them take effect automatically (i.e. without having
the need to stop in u-boot console and issue the env default command).
I see the new values if I use the env default command.
Since I am applying the new config via a RAUC bundle and some systems are
using automated testing it is not practical to issue env default on each
board.
Is there a way of telling u-boot to load / use the read-only / built-in
values instead of the ones stored in env storage?
Current behavior I am seeing in my setup is that old values stored in  env
take precedence.
I have dedicated storage in eMMC for env variables, which is configured via
<my_board>_a53_defconfig  like this:
CONFIG_ENV_OFFSET=0x3e0000
CONFIG_ENV_OFFSET_REDUND=0x3e0000
CONFIG_SYS_REDUNDAND_ENVIRONMENT=y

My platform is a TI Am64x.

Thank you in advance for your attention.

Thank you,
Mircea