Upon further investigation I think this was created, somehow, by StableBit Scanner. When it detected the damaged drive I had it attempt to recover files and the export folder for those was to be the root of E:\Public, but for some reason it may have made an entirely new drivepool. No idea how or why. It didn't put them in E:\Public but created D:\Public.
It does appear the two drives should have the same contents but they don't:
DrivePool(D:) only actually has 7 files totaling 231 GB, which are the 7 files that were restored during the StableBit operation. There are no hidden files, no poolPart folders on this disk. It isn't a physical disk. It is, somehow, a pool that only shows the recovered files and they already also exist on the DrivePool (E:) - I was able to find them in a poolPart folder on one of the disks that make up that pool, with a file modified time from when they were moved off the damaged disk. So, this D somehow contains essentially 7 pointers to files on other disks. There is actual content in the file, so the pool part is pointing to two places? I don't get it. I didn't think a pool worked like this, where a file can be in two different pools simultaneously, or that a pool could contain only 7 files from a disk and not the entire contents of the drive. I'm reluctant to change it since at this point I don't really have a reasonable expectation that simply removing E: from the D: pool will set it back to normal.
I suppose, worst-case, the pool can be re-created from scratch and the data won't actually be lost. Quite odd.