I also ran into this problem and had to use one of the workarounds. I was curious if the latest program update (dated 2/17/2021) may have fixed this, and I tested it out on a backup of my file...but unfortauntely it looks like the bug is still there and it's still grabbing/populating the data from the first ESPP entry when working on the second, and ending up with a $0 cost bais for the second entry. :(
