I was still not able to reproduce this issue here. I followed the steps you described, including enabling/disabling the connect on startup option, and it used the correct nickname every time.