SCT does not install wud images. You still need to use the newer version of DiscU to extract the app, h3, tmd, tik, and cert files. There are also settings that everyday users should beware, as they can cause bricks. So it is not recommended to use the tool. If you aren't stupid, go for it. There is even a version for Sysnand (although still requires sigpatches to launch).
That said, it does not have any additional features such as extraction of corrupt or incomplete packages. They must still pass security tests if you do not have sig patches. With sigpatches, the security checks are bypassed but file integrity is still "
checked" during installation since it will run into a problem extracting, and then will do a roll back and delete what it did install.
This could likely be patched using mocha (not actually sure if this is a SCT thing or MCP) but it would need to be added and would do the same thing cdecrypt does with incomplete packages, run til it hits the dead spot. It might be worth noting you can replace content files using FTPiiU Everywhere without issue. However, be warned, if you replace content of something in a System Title and it does not work, you will brick yourself or have problems recovering.
Be safe and just stick to wup installer. There is no need for an incomplete wud when you can repack one with NUSPacker by
@timogus. If using nuspacker to install file modifications, you may need to fix the tmd, fst (code folder in general may need fixed/replaced with originals) and tik files , so be sure to back them all up for the title in question with ftpiiu everywhere.
Good luck with whatever you're doing, dont brick yourself. Try everything in rN first.