A Japanese user (in the same circle as original reporter @ Nekoru_cat) has found that there has been inclusion of ntfs.sys driver 6.2 (from 8 era!) in the problematic KB5067878 and preview update, whereas it should have been 10.0.2, which they shipped out with the latest KB update.
This is the core driver for the NTFS system, which could explain why the problem were so widespread. From some severe cases, it has been speculated that there were some changes in NTFS. Seeing there were no physically odd behavior from the SSD, they turned the attention to the changes in the update, and while digging through componets related to NTFS, the group of users discovered this.
The fact the newer patch included the version that was supposed to come out with the previous patch suggets that Microsoft had found out about the issue, which is contradictory to their statement.
*This is not at all conclusive, and only initial findings, and hypothesis. please do not jump to the conclusion too early before there are any sort of statement, or more testing.