As I, in turn, said, a process running via nohup most definitely still is associated with a login session and a controlling terminal. After all, if it were not, there would be no point to the gynmastics of ignoring controlling terminal hangup.
nohup is a simple chain loading program that does two things, redirect standard output and ignore the hangup signal, before chain loading the target program.
Here is the code of nohup from FreeBSD, from NetBSD, from OpenBSD, and from the TENEX C shell. As can be seen, there is no manipulation of sessions or controlling terminals.
