Sure
tc-config doesn't call anything, after that the ball is back to init.
Init then launches what it is told to do after-boot; it autologins as root.
Root immediately logs in as user tc, using exec to not leave a root shell behind.
As user tc logs in, his login profile is executed. This checks for the bootcode "text", and if not present, starts X by starting .xsession.
Or, file by file:
init -> tc-config -> init -> /root/.profile -> /home/tc/.profile -> /home/tc/.xsession