Custom entity names with translated components are not handled correctly in command selector arguments. It appears that the name selector argument checks if the entity in question has a resolved name equal to the parameter value, which doesn't make sense for translate components as this means commands may differently depending on client language.

To reproduce (singleplayer):

1. Set your language to "English (US)"
2. Run the following commands in a new superflat world free of entities:

/summon minecraft:armor_stand ~ ~ ~ {CustomName:'{"translate":"entity.minecraft.armor_stand"}'}
/execute if entity @e[name="Armor Stand"]

The output should indicate that the test passed.
3. Now, change your language to "English (Canada)" and again run

/execute if entity @e[name="Armor Stand"]

The output should indicate that the test failed.

I would expect that commands would have the same execution results regardless of client language. On multiplayer servers, commands run as if the language is "English (US)" regardless of client language.