Certainly the problem(?) of X running on TTY2 exists for me. It started with the last update. Though my autologin is working fine.
I’m seeing all of the bootup messages on TTY1, then it’s switching to TTY2 for X (I can see the bootup messages by going to TTY1).
I’m very suspicious that opening X on TTY2 is at the back of the problem I and some other people have of programmes triggered by autostart or systemd timers being unable to open the X server.