So the gap is part of the ripped recording, and therefore already in the database. That makes sense.
Thanks for the extra info, but it is also obvious when one looks closer. I was working on a bootleg last week where the bootlegger had trimmed all the gaps from the tracks to make more music fit on a CD.
The bootleg CD had been lifting tracks from various albums. I had been listening to them played back at the same time as the album as I was trying to calculate what else this bootlegger was trimming from the start and ends of the tracks. That was pretty clear that the “gap” was on the end of most rips EAC had made of my CDs. The Bootlegger had created a gapless CD (and butchered many intros and outros). This was mirrored in the ripped tracks.
Pretty sure this is standard for the players I use. And I have a lot of concept albums that would just sound weird if there was gaps inserted by any player. KODI, VLC, Winamp all behave like this. So does my Android phone and the stereo in my car.