Or perhaps... we forget about the advanced menu and just make the import private key function available, but the user is prompted with an option of sweeping the funds when they do it. Like when they go to import the key it will show a message like "If someone else had this private key before you, your funds may be stolen. You can eliminate this risk by transferring the funds into your other secure addresses. Would you like to sweep the funds into another account?".
Problem solved. You're welcome.
I would have that prompt off by default and not even bother with the explanation, and if anything, have an option in the advanced menu that turns that prompt on. So, by default, one can only "sweep" a private key. BUt if they go to the advanced menu, they could turn on a checkbox that gives them the choice of sweep/import each time they do it. And that's a HUGE if. I think if users can sweep keys, there is no good reason for them to import them into their wallet, and plenty of reasons for them not to.
The main advantage to importing versus sweeping is a) seeing future funds in your wallet if you're expecting them, b) preserving the bitcoin-days-destroyed and number of confirmations, resulting in a far less likelihood of needing to pay a fee to immediately respend the money. Advantage A could be offered with a checkbox: "Remember this key and sweep any funds that arrive in the future?" and a boolean flag on the address that prods the client to sweep any time incoming money is seen. Advantage B is relatively obscure and only those experts who are micro-managing their wallet should care to control it, especially if the coin selection algorithm is decent. Someone with that much expertise and that much desire for control already understands the command line anyway, making it arguable that an import option is good enough when restricted to the RPC API.
