Disconnect vs SIgn Out on Windows RDC

I'm wondering how different end-of-session protocols affect Windows Server performance or anything else. On our Win10 server, users can either "disconnect" or "sign out".

I sign out every time after a session, unless there's a long process running that I need to complete. This can take a while - I wait for 5-10 minutes on a "please wait for user profile service" blue screen. Logging on similarly takes me 10-15 minutes.

I learned that other users always use "disconnect", essentially always remaining logged in, largely to avoid the long sign-in/sign-out wait time that I experience. Is there any disadvantage to this approach, or can I adopt it as well? My intuition is that keeping 5-10 users perpetually logged in degrades the performance of the server or possibly costs our company money, but I have no evidence to back this up

Personally, I always "Logoff" from a RDP connection, in order to avoid various issues, the biggest one being that my password could expire and if it does while I'm still "connected" to a server, then my account would enter an "account lockout" loop as it would constantly try to authentify to that server.

Another issue that can be avoided is that some programs have issues when more than one instance of their process is running. So if User A connects to the server, launches said process, then "Disconnects", and User B connects later on and tries to launch the same process, he may encounter an error message.

And obviously, when you "Disconnect" from a server, all the resources you used when you were logged in are still in use and won't be freed until you do a "Logoff", which could affect the system in the long run depending on its specs, and how many users connected to it and haven't logged off.