>>46819237 (con't)Consider the look into the prototype era, with Pokémon like Scyther (aka Strike). It has a Katakana name, ストライク, which shows that they've considered it as such from the beginning.
I don't know how else to explain it, but it's pretty common for English/Western names to be filtered through Japanese. Like, all of my cousins born here have both their "Asian" and "English" names, and for some of them, their "Asian" names are just their English names filtered through whatever language they're speaking (whether Japanese or Korean). Other English words are filtered through into Japanese or Korean (Wasei-eigo for Japanese), so when you see enough of them, it's easy to pick up on.
But most of all, just because something is written in Japanese or Korean or Chinese, it doesn't mean a native speaker can find it easy to pronounce it. That's why the idea of a name being Katakana-first then turned into Romaji sounds ridiculous to me, because I have high doubts a native speaker would invented a word that's hard to pronounce in Japanese or Korean, then try to fit a Romaji word to it. It's almost always the other way around; consider the English word "virtual", which doesn't sound like any Japanese or Korean word. Why create a complex, hard to pronounce word in Japanese FIRST, then hope a Romaji/English word just happens to match up?