Okay - replying to my old comment now; here's what I've found:
iMac Pro base model 3.2Ghz 8 core 32GB RAM, Radeon Pro Vega 56, less than a month since purchase
Original issues:
Screen brightness resetting after every hard reboot (I would manually adjust to 50%, but it would reset to almost full brightness - 2 bars from max - with each full reboot).
In the first week, several crashes during sleep. Would either put the machine to sleep manually, or leave it running (so it put itself to sleep); would return the following morning, or in some cases, after only 30 minutes, to find it awaiting login after a full restart, complete with a Kernel Panic error message. This appeared to stop after disabling 'power nap' in the energy saving settings, although other users have had crashes occur (albeit less frequently) after doing the same.
Running diagnostics (holding 'D' after a reboot) turned up the three 'crypto_val' errors mentioned in this thread.
I was uncertain whether any of the above were inter-related ...
Action taken:
Following @1Ronin's earlier message, I decided to bite the bullet, and made a Time Machine backup using a 2TB WD Elements USB 3 hard drive I had going spare.
I then booted into Recovery mode (Command + R) and used Disk Utility to erase and reformat the SSD, then returned to the Recovery menu.
I then performed a clean install of OSX High Sierra (less than 30 minutes), and returned to the Recovery menu (ie without booting into the OS).
I then selected the option of restoring settings (apps, user accounts etc) from Time Machine (effectively reinstalling everything other than the OS from the Time Machine disk, as you would via Migration Assistant) - took maybe 90 minutes max (including Logic Pro, the bulk of the Adobe Creative Cloud suite etc).
Results so far:
First thing I checked was the boot diagnostics (holding 'D' after restart) - no crypto_val error reported. Result!
Second thing I checked was screen brightness; this is no longer resetting after a reboot. Result!
Third thing I checked - OSX version is 10.13.4 (curious here, as I haven't gone to the App Store yet to reapply OSX updates. Pretty sure a couple of patches had been applied since the 'out of the box' state, so these appear to have been added during the Time Machine restoration). I was on 10.13.4 before I began the process this morning, and the above bugs were present.
Can't be 100% certain that the Kernel Panic crashes won't occur again, but will be re-enabling 'power nap' to see what happens here. I'll post an update.
At this point, I remain hopeful that everything works as intended. It does seem to give credence to the idea that a batch of new iMac Pros were cloned from a bad image, and the reinstall of the OS is the fix. Might also explain why Apple hasn't acted more quickly in issuing their own fix? Perhaps the number of affected machines is in the minority - maybe not even affecting their own hardware?