I’m very confused by this. It seems throughout your entire explanation you’re defending the use of wait() in a certain environment when I feel like this misses the point of @DarthFS’s mentioning of Avoiding wait() and why
The primary reason you shouldn’t use wait() is because its frequency is not proportional to framerate. In fact, because of this, there’s no guarantee the code after wait() will execute the frame it’s expected to.
I highly recommend you reread the post provided as I’ve never seen wait preferred in quite some time. In fact, the main reason I’m confused is that you end your discussion with a wait alternative that uses RunService.Heartbeat like @DarthFS advocated.
All in all, instead of exploring obscure edge cases of when something becomes acceptable, you should always just opt for the best practice.