I'd been having a similar feeling, that the game was too open and with no midfield, then I realised that I was the one forcing it. I noticed recently that when I don't have the ball, engaging with an opponent while sprinting seems to make the CPU sprint too. And when that happens, it nails you every time, and stretches out the play. What you then have is a situation where both sets of players are sprinting up and down the pitch repeatedly, creating a void in the midfield area because the players can't get up and down the pitch in time to keep up with the ball that's zipping around the park.
The CPU reacts to how you are playing. I'd recommend anyone experimenting with sprinting when you have the ball, then jogging with the ball. The aggressiveness of the CPU kicks up a notch as soon as you hit sprint. It's the same when you're defending. Approach an attacker at slow speed, sure footed and balanced, and the CPU will slow itself too and reconsider what to do. Sprint into a tackle or even in the immediate area near an attacker and it'll see that you're not balanced and skip right past you at full sprint itself.
So tonight I experimented with avoiding using sprint when defending and attacking unless it was absolute necessary, and it instantly played a far superior game. With the ball, I'd only sprint momentarily to get away from a player, or if there was open space down the wings etc. Without the ball, I'd only sprint to get a defending player into a better defensive position but still at a reasonable distance from the CPU player with the ball. Once I got remotely near, I'd manually guide and jockey by using nothing but the L stick, and when really close, press A to jockey and occasionally use the touble tap of A or R1 buttons to try and win the ball. This makes you approach a tackle while at jogging/walking speed and the CPU reacts by thinking twice about trying to dribble, and waits for support. If it does try to dribble, it's not that successful because you now have a slower approach speed, the CPU's approach speed with the ball is greatly reduced, and you make the tackle. When both sides are sprinting, the CPU beats you every time.
The result? The CPU seemed to react to that and because I wasn't sprinting constantly at the CPU to try and win the ball back, it was playing a slower, more considered game against me. This also meant that players weren't being pulled all over the park and suddenly there were tons of midfield battles. By laying off sprint for most of the time, I was suddenly able to win the ball a LOT more than before, and it also made me more aware of better defensive positioning in terms of reducing passing lanes etc. This also has an effect on how fast the CPU passes the ball. If you sprint all over the place and the play becomes stretched, the CPU will try to exploit that and smack hard, quick passes to try and take advantage of the fact that your players are out of position. If you slow everything down, everyone is closer together, both sides are moving slower, and it has to resort to playing slower, more deliberate passes because your defenders are in their correct defensive positions.
I found the same for attacking, too. By laying off the sprint button I felt like I could dribble better, and best of all, there are far more passing options in attack because supporting players now actually have the time to support you.
But it's definite, try sprinting and you'll see the CPU react accordingly.