Probably not. (Fyi posting screenshots is a really good idea when you ask questions like this....) In order for a new image backup to be appended to an existing image backup set, the partitions must be an EXACT match, which means the new backup must contain the same partitions as those in the existing set, with no partitions added or removed, and all partitions must have the same size and "offset" (position on disk). It's not at all clear from your posts which partition you're talking about that changed or which size is the previous size and which is the current size (again, screenshots!!), but you're talking about your Windows partition and it was originally 58.5 GB and is now 58 GB, and it's not because you did that yourself, then it probably happened because Windows shrank it to create space for a new/larger Windows Recovery partition after it. In that case, THAT partition would be different now too.
You just have to let Reflect create a new Full based on the new partition layout, and from that point forward you'll be able to create new Incrementals as children of that new Full. It's not a big deal.
Also be aware that by default, your retention policy will no longer act on those older backups since the default mode is to apply rules to "all matching backups", and those old backups will no longer be a match. You can change that to "all backups in the destination folder" if you want, but if you do that, make sure your destination folder contains ONLY backups created by this job, otherwise that change could cause Job A to purge completely unrelated backups created by Job B.
Anyhow, it's currently 3:30 AM where I am. I was up working on something else that took a lot longer than expected, but I'm going to sleep now. If you need anything else, I'll check it later.