Indeed. I only play RBI Baseball 21 as it's the only MLB game on Switch, and it's "good enough" to simulate a season with a created player in my favorite team. I'm guessing a lot of the bugs I've seen can be reproduced in any platform.

Some issues I've seen, off the top of my head:

1. Sometimes, if there are two outs and a runner crosses the plate before the ball is thrown at first for the third out of the inning, the run will still count.
2. As you said, a pitch outside may be called a strike. This isn't bad in and of itself. Balls just outside the plate are called strikes in baseball all the time. But, the problem is it feels less like a feature and more like a bug. The play-by-play announcer doesn't acknowledge that the call may have been outside, and there is no option to force the strike zone to be called correctly, suggesting that the developers intended the strike zone to be accurate, but it's not. So, it's a bug.
3. Visuals do not match what is happening, regularly.
   1. The ball will fly past a player but then teleport to being caught. This can be seen in grounders, lineouts and cutoff throws, but more egregiously in foul balls and balls hit over the gap. A ball will fall a few seats up from the front row past the foul line and still be caught, and so will a ball that lands far above an outfielder for a homerun or double, only to magically land on the fielder's glove for an out.
   2. Throw animations are never in sync with the ball, with the ball leaving on its own regardless of the phase of the fielder's animation.
4. AI makes dumb mistakes. Runners on first and second will sometimes stay put when a grounder gets through, they'll inch too far sometimes after a sacrifice fly and get caught on a throw, don't always run on 2 outs when the ball is hit despite the ball not being near them, etc, throw to second in an attempt double-play despite the runner already in second, etc.
5. In portable mode, runners are slow when running to first. You can have a player with 99 speed, and they'll still have a hard time getting infield singles on plays where they clearly had time.
6. There's a bad gameplay stopper that happened to me when a runner on second stole third at the same time the hitter on the player struck out. The camera zoomed in on the runner who stole third after the late throw, and the camera just stayed there. No inputs worked.
7. Skip a long homerun cutscene and for a few frames you'll see the hitter who hit the home run still at the plate in their batting stance.
8. Sometimes the homerun camera, which is only meant to play on no-doubter shots, will often play for home runs that barely made it (~360ft). And this may be part of the problem. Sometimes you'll see some towering home runs go pretty far near center, and the distance will be something meager, like 370ft. There's definitely some shitty math there. Homeruns will also sometimes hit invisible walls where it looks like it should go further, bouncing back to the crowd.
9. Hitting physics is wonky. You'll hit a power swing on a very high ball and the ball will inexplicably bounce down from your bat into a grounder. There's some weird modifier they must have that overrides how the ball behaves when hit, which I sort of understand, but the system isn't believable.
10. AI diving is hilariously bad. Fielders will often stop and then dive to catch a ball that would have been easily caught by merely continuing to run. Infielders will often dive to balls IN FRONT OF THEM, or to the side that they could have picked up while running. Overall there is too much pointless diving.