So the way this works of course is simply that you should not use any of the architecture-specific repositories or packages (and you would not be by default if using a supported install method and correct configuration) .. and hence will not have access to those optimized builds of packages.
It does not mean anything actively negative for you if you do not somehow forcibly use any those architecture-specific packages.
It just means you do not get to make use of some of the things that Cachy offers.
( Optimized packages )
No need to worry.*
This has also been asked before, ex;
* - Though it may be said more generally that Arch, and therefor Cachy, is closer to a niche DIY distro. Besides the rolling release the user is expected to manage certain things like pacnew files. We also have nonstandard things like custom patched kernels. It has nice features but it is not a nanny OS. Inexperienced users can still be successful but they must be willing to learn and get their hands dirty sometimes. So maybe not exactly “no worries”.
THANKS! You give a really fair and complete answer.
As things are just fine, and I don’t mind “getting my hands dirty” doing regular maintennance,… this is fine. P.S.-I only recently did my first management of .pacsave files, but this ain’t that bad. I’m still learning. rock on.