Well I actually can't reproduce this exactly anymore because it seems that snapd schedules the refresh to happen before I can get a shell to the system on multipass,
$ sudo snap debug state /var/lib/snapd/state.json --abs-time
ID Status Spawn Ready Label Summary
1 Done 2020-09-21T19:11:45Z 2020-09-21T19:11:53Z seed Initialize system state
2 Done 2020-09-21T19:11:55Z 2020-09-21T19:11:58Z become-operational Initialize device
3 Doing 2020-09-21T19:12:00Z 0001-01-01T00:00:00Z auto-refresh Auto-refresh snaps "snapd", "pc-kernel"
4 Done 2020-09-21T19:12:01Z 2020-09-21T19:12:01Z configure-snap Change configuration of "core" snap
and this was with a scripted run of calling snap set, so I'm not sure I could do it much faster unless I deliberately slowed down the VM I suppose.
Well I actually can't reproduce this exactly anymore because it seems that snapd schedules the refresh to happen before I can get a shell to the system on multipass,
$ sudo snap debug state /var/lib/ snapd/state. json --abs-time 21T19:11: 45Z 2020-09- 21T19:11: 53Z seed Initialize system state 21T19:11: 55Z 2020-09- 21T19:11: 58Z become-operational Initialize device 21T19:12: 00Z 0001-01- 01T00:00: 00Z auto-refresh Auto-refresh snaps "snapd", "pc-kernel" 21T19:12: 01Z 2020-09- 21T19:12: 01Z configure-snap Change configuration of "core" snap
ID Status Spawn Ready Label Summary
1 Done 2020-09-
2 Done 2020-09-
3 Doing 2020-09-
4 Done 2020-09-
and this was with a scripted run of calling snap set, so I'm not sure I could do it much faster unless I deliberately slowed down the VM I suppose.