Hm, for the last couple of kernel updates (I am on 7.1.13-200.fc44 now) rotation has worked for me, so I had the impression the module load order was fixed more permanently now. But if people are having mixed results with the standard setup on the same kernel then it would seem the module load order might not be entirely deterministic.
A workaround would be to write a “SUID” script that reloads the soc_button_array module upon login to gnome. The execution upon login can be done by putting a .desktop file in .config/autostart that calls the “SUID” script. That just automates the reloading of the modules in the right order, without having to touch the core system startup configuration.
An alternative is documented elsewhere: instruct dracut to include the modules in the initramfs from which the kernel boots the first time.