My Biases
I’m the opposite from you; there’s some stuff I am okay with them being forced into being mini, since 1/16,256 to randomly roll for a size mark is a pain.
Now with my biases explained, let's go on and discuss.
4 key points you need to know:
1. When the hyper training issue (from transfers during initial HOME launch) was a thing, they acknowledged the issue, and fixed it promptly. [This shows they’re capable of checking their logs and digging out initial entries and combining initial unmoved data and mixed data]
2. When the GO Lv 1 transfers was detected to be a bug on their part, they acknowledged and fixed that (by having them correctly reflect as lv 100). However, notice how they didn’t revert to the level the Mon that was sent into HOME, despite the fact that they have logs and could have checked.
3. They *did* fix the 0 scale issue, but from a different perspective; LGPE XS and GO XXS mons doesn't retain the size when shifted into HOME, because the size were forced to rerolled; they acknowledged it and fixed that. Notice how they didn’t do anything about the issue you have in mind.
4. You may want to read up on all the issues they have had. I won't be discussing all of them, but some may show up.
With those 3 key points out there, lemme discuss *why* I think the fix wouldn’t happen.
1. No public acknowledgement nor announcement.
Whenever there is an issue, they’ll acknowledge it and work on and fix it. What you described isn’t acknowledged (that I know of) and thus not fixed.
2. Issues along the same vein or core were fixed 6 months ago.
They already fixed issues tangentially related to the one you have in mind (like 6 months ago), but ignored the scale 0 thing. Given the proximity, you would think they’re aware. This suggests they wouldn’t/doesn’t want to fix it.
3. Do they even see it as an issue.
"Canon in player's-mind" thing - since you’ve already seen it as mini in PLA, it would be weird for it to suddenly become XL when shifted. But I can’t say for sure.
Data the player normally cannot see - given height/weight/scale are hidden data-points that the player should not have been able to witness directly, and the HOME's implementation of the hidden values should not have been determined, perhaps them screwing up the randomness was not a big deal in their head?
4. Timeliness.
If there is an issue, they tend to fix it within a few weeks or at most a few months from the time frame that it occurred (I think that is the maximum, being the Nincada/Shedinja tracker issue). Not half a year.
5. Other issues that should have been fixed
Commonality is that they exceeded the time-frame.
Spinda - Spinda EC was set incorrectly by BDSP; important as EC determines the spots. Was acknowledged to some degree, by the presence of their 'fix'. Their 'fix' was to prevent entry and exit via BDSP, instead of playing around with the EC.
Totems-sized Pokémon - These Pokémon from SMUSUM are taller than what you regularly catch, and tower over regular captures. In the game-data, how the game recognizes them as separate, is that they have a different form ID. When transferred via HOME, they lose that status and get set into the regular species. Since SWSH nor BDSP doesn't show HT/WT in game, there is no 'canon' in terms of sizes, and the least they could do is retroactively max out their scale. Wasn't acknowledged, wasn't done.
Personal Conclusion
Using factors 1 to 5, I believe HOME won't retroactively fix it. There's no acknowledgement for that specific issue. Issues surrounding the issue has already been addressed. Do they even see it as an issue. It's been 6 months since the fix for related issues has been completed. It will likely fall under the umbrella of other issues that should have been fixed.
But that is just my personal conclusion based on the years I've seen them operate. They might suddenly be compelled to fix it, even though it has been left in the corner of the dusty room this entire time. I don't work for them. Who knows really.
Have you tried sending a support ticket to them?