Any recommendation about whether something should be avoided as archaic
(or deprecated if one prefers that term) is a personal one rather than
one in the standard. Just because the standard doesn't have such
recommendations doesn't mean they can't be darned good ideas.

I personally consider things like DCOS to be archaic, and I recommend
never using it. I'm not going to waffle by saying "rarely". I mean that
"never" literally. Yes, I know you can invent a case where one could use
it. But such things are so rare that I do not recall ever once seeing
such a case in code "in the wild", as opposed to code where people are
trying to illustrate how it might be used. I supose my recollection
could be faulty, but again I mean that "not once" literally.

That puts it in the category of things whose utility is so low that I
believe one is better off ignoring completely. If you do happen to know
about the feature, pretend that you don't anyway. The only times you
even need to know that the feature exists is when you are reading old
codes.... or when you are explaining to someone why they should be
ignoring the feature.

If there ever actually was a reason to pass a specific intrinsic as an
actual argument in real production, I'd wrap the generic version in my
own specific rather than use the standard one.