The Japanese analogy is a good one, because it reminds me of when WW2 was over, a few Japanese refused to believe they had lost and kept on fighting, just as you are clutching at your belief, (good on you), but it is clear from signals in the wider community that you are fighting for a lost cause. That's not to say you can't call it whatever you like, just don't think the majority will be there with you.
The purpose of language is to be understood. I need to use vocabulary that is accepted by the largest percentage of the community.
Given the poll results, "bit" is okay with ~55%, "satoshi" is okay with ~75%. To get these numbers you just compare the total number of participants with how many of them did not click the respective checkbox.
If this trend ever reverses, then I will immediately switch to "bit". But right now I see no reason to do so.
On usability, if you want to argue that, put up some use cases to demonstrate your point.
My use case is explaining Bitcoin to newbies:
With satoshis, all I need to explain is that 100 million satoshis = 1 bitcoin.
With bits, I need to explain that...
- ...100 satoshis = 1 bit, and...
- ...1 million bits = 1 bitcoin.
I very much care about reducing complexity from my website, so every bit matters.
oops I diverged again into the bigger picture, not specific to your website/faucet, I take it all back.