Maybe with CNC firmware the controller doesn't have a way of knowing, but Klipper (one of the more popular 3d printer firmwares on printers comparable to Bambus) always looks ahead. Eg if you had two commands to move in a straight line at the same velocity, Klipper will not do the first move, slow down to a stop, then start to do the second move, it'll look ahead and see that it can keep accelerating in the same direction until it reaches the point where it'll have to start slowing down to arrive at the final point while staying within the configured jerk and deceleration limits.
It always has the ability to lookahead and adjust the commands to the steppers. As a result it does not matter if you specify whole arcs or specify them as small lines, because either way it computes the same X and Y stepper positions and velocities.
The 3d printing community is full of tons of enthusiasts who put in a large amount of time, money and effort into devising methods for maximizing the speed and quality of their printers. Despite all the scrutiny, arcs are seen as optional with inconclusive benefits in terms of print quality/printer noise (since, again, most of those enthusiasts are running Klipper).
It always has the ability to lookahead and adjust the commands to the steppers. As a result it does not matter if you specify whole arcs or specify them as small lines, because either way it computes the same X and Y stepper positions and velocities.
The 3d printing community is full of tons of enthusiasts who put in a large amount of time, money and effort into devising methods for maximizing the speed and quality of their printers. Despite all the scrutiny, arcs are seen as optional with inconclusive benefits in terms of print quality/printer noise (since, again, most of those enthusiasts are running Klipper).