That's not really the point though right? It means that pulling and using containers that are destined for x86 will require also building arm64 versions. Good news is buildx has the ability to build arm64 on x86, bad news is people will need to double up their build steps, or move to arm in production.
What they talk about is Rosetta's macOS frameworks compiled for Intel being kept around (which macOS Intel apps use, like if you run some old <xxx>.app that's not available for Apple Silicon).
The low-level Rosetta as a translation layer (which is what containers use) will be kept, and they will even keep it for Intel games, as they say in the OP.
In addition to what others are saying, I think it's important to think "apples to oranges" here.
Think about it this way, if you're a dealer you want to inflate your supply right? So, if you have a street drug that is an 'upper' and you want to cut it, you need to cut it with uppers, or something that can mask an upper. That cut needs to blend in, if you're expecting something blue, and it has red in it, then you'll know its off.
Psychedelics would need to be cut with other psychedelics, but it's not as easy as mixing two things and having it come out. LSD comes as a crystal and is then put in an alcohol solution and dried on paper, there's not many things that would work that way. If the goal is to stretch your supply, you just further dilute it, and many people do.
Where there are cheaper/easier alternatives are things in the 2c family, or others that are _close_ to the experience of LSD but not, and are also more toxic.
I don't know if any of that is clear, or makes sense but
