Well that depends if you don't mind using SX Pro to boot your CFW forever or if you want to have the chance to boot CFW in other ways in the future. See the Nintendo Switch has these things called fuses and some of these are used to prevent downgrading. When your console normally installs a system update and reboots. When the console's stock bootloader detects you are running a firmware higher than your current fuse count, it burns fuses until they match. And in order to prevent your console from downgrading, the stock bootloader will not allow you to boot a firmware lower than the current fuse count. So in order to prevent fuses from being burnt, we install firmware files
and AutoRCM where AutoRCM prevents us from using the stock bootloader. This is how ChoiDujourNX works in order to update your firmware without burning fuses. However as you said, it may flag your console for a ban since it requires the usage of CFW & homebrew. But there are other ways of updating your firmware without burning fuses.
The first method involves updating the console with AutoRCM enabled while running CFW. You may have asked, "If AutoRCM can be used to prevent fuses from being burnt, why not just update with AutoRCM already enabled?" The reason that is not possible is because system updates normally remove AutoRCM. However free CFW can prevent this. This is not a feature of SX OS and may never come to the CFW much like the other features of free CFW such as overclocking and external sysmodule loading. Anyway, installing a system update with AutoRCM enabled while running a free CFW will not remove AutoRCM thus preventing your fuses from being burnt. But this still requires the usage of CFW which means it still has a chance to ban your console. There is one more method of updating without burning fuses.
The last way involves manually applying AutoRCM after the system installs the system update. There is technically a way to prevent the stock bootloader from burning fuses without CFW and that involves putting the console into RCM before it has the chance. This is the safest method in terms of a ban since RCM and AutoRCM are next to undetectable but it is also the most dangerous as failing to boot into RCM will burn your fuses. If you wish to try this method, I recommend following this
guide.
Or if you do not care about other exploits and are content with using SX Pro until time immemorial, then you can just ignore the walls of text above and just update to 9.0 normally once SX OS supports that firmware.