Now we are getting somewhere.

X windows system implicated. Though the 2d video shows how fast the shortcut boot is, I thought I should get a firm number so I did the shortcut boot and logged in to get output of 'systemd-analyze critical-chain' and I got the following very interesting responses, shell dialogue copied below. The same processes (I would assume) are hanging for 1m44s, but the shortcut somehow allows the user to log in while waiting for them to finish (as well as solving the other problems of clipboard and screen size, which seem to go with the more primitive login screen). Whether those processes should take 1m44s or not, I don't know, maybe it is normal, but the user should be able to log in before they are complete, as I can do with shortcut boot. If those processes are taking inordinately long, then shortcut boot gives opportunity to log in and catch them as they struggle, as seen below. The time I had to wait to get the critical-chain result was about as long as I had to wait to log in at all, under stock 19.10 without shortcut-boot procedure:

wift@stock19:~$ sudo -i
[sudo] password for swift: 
root@stock19:~# systemd-analyze critical-chain
Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
root@stock19:~# systemctl list-jobs
JOB UNIT                                 TYPE  STATE  
 48 setvtrgb.service                     start waiting
137 system-getty.slice                   start waiting
  1 graphical.target                     start waiting
102 systemd-update-utmp-runlevel.service start waiting
 83 plymouth-quit-wait.service           start running
  2 multi-user.target                    start waiting

6 jobs listed.
root@stock19:~# systemd-analyze critical-chain
Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
root@stock19:~# systemd-analyze critical-chain
Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
root@stock19:~# systemd-analyze critical-chain
Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
root@stock19:~# date
Sun 19 Apr 2020 10:50:27 PM EDT
root@stock19:~# systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 44.881s
└─multi-user.target @1min 44.881s
  └─xrdp.service @1.496s +1.036s
    └─xrdp-sesman.service @1.474s +20ms
      └─network.target @1.470s
        └─NetworkManager.service @1.381s +88ms
          └─dbus.service @1.379s
            └─basic.target @1.375s
              └─sockets.target @1.375s
                └─snapd.socket @1.373s +1ms
                  └─sysinit.target @1.372s
                    └─systemd-timesyncd.service @1.175s +196ms
                      └─systemd-tmpfiles-setup.service @1.160s +10ms
                        └─local-fs.target @1.158s
                          └─home-swift-shared\x2ddrives.mount @11.731s
                            └─local-fs-pre.target @177ms
                              └─lvm2-monitor.service @116ms +61ms
                                └─dm-event.socket @115ms
                                  └─system.slice @110ms
                                    └─-.slice @110ms
root@stock19:~#