Its a CT entry. Maybe your not understanding what I'm saying. When you share an NPC its got to be on the CT and friendly. Just part of the rules. So when you do that the only thing you will be "changing" is the CT entry. If you share something from the CT it is with the intent the player control it. Like a PC. Now a lion - like a mule - really does not have anything that a player should be messing with. But if you gave it to him - you risk the CT entry being messed with. Just like giving a player a PC risks them messing with it. Neither should be done. Both can be done without the GM realizing it. So if you don't trust a player to not mess with things - too late. They have the PC to mess with. Giving them control of an NPC is no different.
I'm not sure how that can be logically reasoned that it is. If you don't trust them not to mess with things out of the GM's attention then... game over man. Game over! Adding a CT NPC entry into the mix on that - well - 1/2 glass full argument to me. If the CT NPC entry is part of the encounter - not sure why you would pass it onto a player unless they were doing something for you like being a 2nd DM helping you run NPCs. In which case, yeah - you'd want full control.
And to repeat something I added in my last reply pretty late... And while the CT NPC entry is not permanent like the PC, I create a "Player NPCs" group in the NPC button where I occasionally back up the NPC for them in case I accidently clear it out of the CT ( that way they don't lose their inventory - but the correct way is not to accidently delete it out of CT - I'm just error prone so I do this to guard against it - which is why I'm developing a combat groups extension to allow me to remove it from CT without losing all the stored CT stuff ).
That insures I don't lose anything due to my incompetency as a DM (yeah its a thing for me).

