Skipping strokes is always worse than having a diffirent stroke length. And in the case of the handy, it will already restrict the movement speed if its too fast (it can handle 600 units per second in OFS). Short moments of exceeding that speed in the script will be fine (a second worth of 1000ups will be handled fine), which on that could be good for devices capable of handling such speeds.
However, scripting wise you can decide to do 3 things: you either just script it accurately ignoring speed. This means speeds of 1000 can happen in some cases. By leaving the script as it is, you will provide a high accurate script and can just rely on software to cap the speeds. This is quite recommended to do because of the 2nd thing you can do:
You can parse the script to a speed limiter (funscript.io has this feature), and this can make it capable to be used on the handy (note their handy limit says 400, while 600 can be easily maintained). By using this after the original, the small diffirences in the original are generaly preserved, but the stroke lenghts are reduced. This is again a good thing to do.
You can also decide to script to the limit yourself and make the diffirences a bit more excessive. This can amplify the nuances of the movement, but still… at this speeds it mostly is going to be unnoticed. This generaly only works when the videos are not going to excessive speeds, and is quite a hassle to do as you will constantly be fighting the speed. Its better here to at least allow some excessive strokes to exist (the device will limit this).
For timing, if its off by 1 (25fps) or 3 frames (60fps) to keep within a limit, it wont be noticed as long as the important movements (usualy downstrokes) are prioritized into accuracy here. Usualy because the downstroke has a better audible sound, it is what your brain will react to.
Never however miss a stroke or add 1 too many. This will be noticed. Transitions between scenes on that can in some cases be awkward here though. And in that case, missing a stroke is not an issue as long as the experiences remains. A half stroke can be used in this case for example (for example the previous motion was moving upward to the tip, but 1 frame after on the next scene its back at the bottom. in this case preserving the movement is better. not having movement here would be odd).
Its often also better to keep movement simple. The material of sleeves can already react significanlty diffirent, and in some cases stuttering or speed changes can be quite well noticed. Adding too much points isnt going to help here (even if the points try to make a smooth curve, if the movement is slow it just doesnt work as the device will still react in a very sudden way and by that give some sudden force). The faster the script goes, the less this will be noticed, until the device has to react too fast (causing it to feel like vibrations - which in fast strokes generaly just stop the movement for a frame).
In the end though, each scripter has his own style. And what feels best for you is just what you should go for (again, this is why testing your own scripts is important). Even if the style of scripting is off, it doesnt matter. People can differ a lot in preferences (some like vibrations, some dont, some only in limited sections).
)
