Seems you are pro in robots and AI. I wonder, if the robot calculates the spin and drop point only according to the trajectory o f the ball, how long (time) and how far (the length of the trajectory) does it need to do the calculation (with no limitation of cameras)?
The I doubt it would take a millisecond. Much depends on the CPU power but the problem can be divided up among X, Y, Z coordinates. However, there is a lot of calculations that must be done.
First one must take into account the frame rate of the camera. Lets assume the frame rate is 100 FPS. This is 10 ms per frame and it takes about a second to for the ball to move to the other side. I was watching the speed indicator on the net and it was saying 3 to 4 meters per second. So would need only about 100 iterations between when Dan hits the ball and the robot hits the ball. There is no need for to do this unless trying to predict the ball's trajectory or better yet, to pick a location for the ball to land and minimize the time it takes for the ball to get there. This may take more iterations but it is easy to do. This would be necessary to compute the paddle impact speed and attitude of the paddle.
If the robot can pick where to land the ball and minimize the time of flight, the next step can be taken which is to chose the best place to land the ball to be most difficult for the opponent. I think this qualifies as attacking.
If the robot knows the in coming spin then it will be able to correct the angle of the paddle rather than just assume the ball will bounce off the paddle like a mirror.
It would be interesting to know what kind of rubber the robot was using. This data can be learned by trial and error. It would also need to update or tweak these parameters as the ball or rubber changes.
I have done the calculations for the trajectory of a TT ball given an initial speed, angle from horizontal and spin. These three parameters would need to be adjusted to find the values that allow the ball to land at a desired distance. Flatter trajectories will take less time but will also be riskier due to passing over the net with small margins.
This would be a fun project. I don't think the limitations are due to software or processing power. It think the limitations are mechanical.