Clients should just pick one relay (maybe the  fastest one or lowest latency) and a secondary fallback when fetching events from another user. Having many options would only be bad if clients don’t apply any optimization strategy.
Users can’t make good choices if they don’t understand the implications of this inbox/outbox setup. Assume they will do it poorly and code accordingly. 

 But I do think choosing a Home relay is key for any new user. If you don't know where your notes are, then what's the point? 

 Education must not be circumvented .. devs should not make choices for users - else you will become #Apple :-)  

 Yep 

 There should be articles explaining all of these concepts, and I hope users learn them in due time but Nostr works just fine for the average user without it. The outbox model is an optimization. 

 Could you get away with just using general relays for a new user, then a while down the road (a few posts, a few days, I don't know) send them to an article describing how to pick a home relay? 

 Tried it, but people don't change default settings. We have to add more interesting measures to get people to take control over their data.