I run Solus with LVM on LUKS on two laptops. After this weeks update rd.luks.uuid boot option disappeared from both the old and the new kernel entries on my work laptop making it unbootable. After adding it explicitly to /etc/kernel/cmdline and running clr-boot-manager update the option was added back. Note that on this laptop Solus is the only OS and was installed to use the whole disk with LUKS enabled during installation. On my personal laptop I also use LVM on LUKS but it was encrypted manually (installed to plain partition on an external drive and than moved into an existing LVM on LUKS container adjusting the boot loader entry accordingly). With the last update boot entries were updated correctly on it, rd.luks.uuid wasn't lost.
I'm not quite sure if it's a corner case in clr-boot-manager update or something weird happened during the update. Let me know how I can provide more useful information to help to resolve the issue.