Eh, I think it's fine as it reduces friction to getting the data. People particular about using KJV or whatever can easily switch. I'm more surprised Cherokee is one of the supported languages!
I used to work a a Bible software company, many, many years ago, and had to write a similar API. The surprise challenge I ran into, as that API was meant to support multiple translations, was that they don’t all agree on where chapters and verses start/stop. Some translations include or leave out a verse or two compared to others, and in some cases will number verses oddly to show it (like skipping from verse 20 to 24 because the translation chose to leave out 21-23), which could cause “verse 24” to refer to different verses depending on the translation.
Often or always(??) it is caused by word ordering requirements in the language -- think subj-obj-verb
When translating orally, it sometimes means a translator has to pause, or guess at how the speaker is going to end sentences/paragraphs. This is because the other language requires an ending element to come earlier
This also has a fun impact on jokes. Sometimes the punch line needs changing, or other jokes become possible -- because the sentence ending gives a different denouement
--
Biblical Greek tends to use word order for emphasis, but still with an overall sentence structure very similar to English. So (as far as I know) the issue is mostly hidden for English speakers
