If thread blocking is a problem then your example would stutter at every await. VS using https://motion.dev/api/timeline or Framer Motion both of which can sequence complex WAAPI animations.
await is only used to build the non-blocking timeline: Think keyframes, not frames.
If you instead build the keyframes up front and give them to WAAPI/CSS then you won’t encounter stutters.
This is easily provable by adding some blocking JS into your code. Block the main thread for ten seconds after your first transition and see when that next await triggers. Your animation will run smoothly for 1 second and then the next chunk of your timeline won’t run for another 9.