2. The slave list does not hold the sorting set. After entering the slave profile and leaving, it returns to the alphabetical order of names. This makes operations very difficult. Especially when there are many slaves.
3. Tiring system for adding nicknames. Its ruins alphabetical system on the slave list (only for use, ignoring different sort settings after each exit from the list). There is no option to completely disable this annoyance.
While I agree with the issues about the slave list's ordering (and naming), I actually used the nickname effect to help me manage them: I give them nicknames related to what I have to manage about them (so, mostly: "Spa" to get them obedien and fearless, "Devotee" to make them...devotees, "Sex Training", "Muscle" or "Race"). This way, the alphabetical order actually organises them depending on what I am supposed to manage about them and I don't have this sorting problem, and I remove the nicknames once they are optimised for the destined job (which is when I more or less stop having interactions with them).
I also use it to keep track of special cases, most notably "my" children: the sorting option for the slaves' origins is particularly hard to use, and when checking for those born on the station, there is no way to isolate those the MC actually sired...
I will add something else about the interface: several events are specific to named slaves. Unfortunately, we don't have the details about them, and do not even have their picture. It is most bothering when the slave ring (I don't remember the name right now) offers to buy one out (actually, this is along the lines of your issue #6, since this could be a way to go to the slave list, check out which slave they are planning on buying, and then go back and tell them if we accept or not).