Yes, it's another issue which would need attention before we add cryptsetup prompt to usplash. I don't think that adding current cryptsetup init.d processes to initramfs is a acceptable solution, cryptsetup should still be started from init.d at this stage and when it is configured this way. Keeping the actual configuration until the bug gets fixed is clearly not a problem, it just don't give a good user experience because it doesn't look great, but it works correctly.
IMO, This cosmetic bug should only be fixed if it doesn't cause any regression.
Yes, it's another issue which would need attention before we add cryptsetup prompt to usplash. I don't think that adding current cryptsetup init.d processes to initramfs is a acceptable solution, cryptsetup should still be started from init.d at this stage and when it is configured this way. Keeping the actual configuration until the bug gets fixed is clearly not a problem, it just don't give a good user experience because it doesn't look great, but it works correctly.
IMO, This cosmetic bug should only be fixed if it doesn't cause any regression.