Sorry to burst your bubble, but it is likely illegal.
At first glance, the name looks legal:
However if you go into the trash bytes of the name (trash bytes -> bytes in data after the name is terminated. After the 0x00, in this case the 0x00 is from $08 to $09):
there's extra characters at the end, after the Korean name!
If you convert all the hex to UTF16 string:
You see te from Omanyte.
It is normal for Pokemon to have trash bytes in their nickname. However, IIRC, it isn't normal for Korean unevolved Pokémon to have English trash bytes in their name, especially from the English species name.
In this case, I reckon someone hatched/genned a English Omanyte, then changed the language in PKHeX, not realizing the trash bytes would remain.
And to preempt the 'why PKHeX doesn't validate trash bytes?', I think it tried but what happens is that there are many many scenarios that trash bytes can exist. And they vary from game to game. And some transfers removed trash bytes. I remember PKHeX used to validate basic trash bytes for a while but no idea what happened to it. In any case I don't think Switch games check them for trades, but HOME clearly does.