Hi NedPyle thanks for letting us know.
May I share some thoughts and questions?
1. Could it be the "lazy-writeback", introed and enabled by default since 1809 builds could be a cause?
Even when not utilizing SMB over network but usual local copy jobs e. g. from / two nvme one might notice a massive jigsaw effect when copying solid bigger files, especially with File Explorer, not so much with Robocopy as of its nature of multithreading.
Unfortunately there is no flag such as ADMX / CSP to disable lazy write-back for Explorer, to revert to the default behaviour of Windows Client and Server versions before build 1809.
The fact unbuffered IO does help, could be indicating this.
2. Could you exlude the now wider default use of SMB compression, to be a potential cause for the issue?