Oh, let's see. If I recall correctly, there's some type of assume clean/good or the like. The (potential) downside of that, is if it's not actually clean/good, or has missing or corrupted data ... but other than that, I think it ought work. So, let me see if I can throw together a quick test/demo of it - and in this case it will actually be good/clean - I can't speak for your actual drives or their data. So - I think maybe I'll (mostly) skip the comments on it, and just show commands/output. And may omit/trim output some fair bit for brevity/clarity (and space savings).

# cd $(mktemp -d /tmp/md.demo.XXXXXXXXXX) && df -h .
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           512M  768K  512M   1% /tmp
# (for d in 0 2 3; do truncate -s 134217728 "$d" && losetup -f --show "$d"; done)
/dev/loop0
/dev/loop2
/dev/loop3
# mdadm --create --level=raid5 --raid-devices=3 /dev/md53 /dev/loop[023]
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md53 started.
# grep . /sys/block/md53/size
516096
# factor 516096
516096: 2 2 2 2 2 2 2 2 2 2 2 2 2 3 3 7
# perl -e 'print(2**(13+9),"\n");'
4194304
# dd bs=4194304 if=/dev/random of=/dev/md53 count=63 status=none
# < /dev/md53 sha512sum > sha512sum
# mdadm /dev/md53 --fail /dev/loop2 --remove /dev/loop2
# losetup -d /dev/loop2 && rm 2
# mdadm /dev/md53 --fail /dev/loop3 --remove /dev/loop3
mdadm: set device faulty failed for /dev/loop3:  Device or resource busy
# mdadm --detail /dev/md53 | sed -ne '/Major/,$p'
    Number   Major   Minor   RaidDevice State
       0       7        0        0      active sync   /dev/loop0
       -       0        0        1      removed
       3       7        3        2      faulty   /dev/loop3
# mdadm --stop /dev/md53
# mdadm --examine /dev/loop3 | grep -F -e '  State' -e 'Data Offset'
    Data Offset : 4096 sectors
          State : clean
# mdadm --zero-superblock /dev/loop3
# mdadm --examine /dev/loop3
mdadm: No md superblock detected on /dev/loop3.
# uuid=$(mdadm --examine /dev/loop0 | awk '/Array UUID/ {print $(NF);}')
# mdadm --create --level=raid5 --uuid="$uuid" --raid-devices=3 --force /dev/md53 /dev/loop0 missing /dev/loop3
mdadm: /dev/loop0 appears to be part of a raid array:
       level=raid5 devices=3 ctime=Sat Aug 30 19:29:47 2025
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md53 started.
# < /dev/md53 sha512sum | cmp - sha512sum && echo MATCHED
MATCHED
# sed -ne '/^md53 :/,/^ *$/{/^ *$/q;p;}' /proc/mdstat
md53 : active raid5 loop3[2] loop0[0]
      258048 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [U_U]
# mdadm --detail /dev/md53 | sed -ne '/Major/,$p'
    Number   Major   Minor   RaidDevice State
       0       7        0        0      active sync   /dev/loop0
       -       0        0        1      removed
       2       7        3        2      active sync   /dev/loop3
# (d=2; truncate -s 134217728 "$d" && losetup -f --show "$d")
/dev/loop2
# mdadm /dev/md53 --add /dev/loop2
mdadm: added /dev/loop2
# sed -ne '/^md53 :/,/^ *$/{/^ *$/q;p;}' /proc/mdstat
md53 : active raid5 loop2[3] loop3[2] loop0[0]
      258048 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
# mdadm --detail /dev/md53 | sed -ne '/Major/,$p'
    Number   Major   Minor   RaidDevice State
       0       7        0        0      active sync   /dev/loop0
       3       7        2        1      active sync   /dev/loop2
       2       7        3        2      active sync   /dev/loop3
# < /dev/md53 sha512sum | cmp - sha512sum && echo MATCHED
MATCHED
# [ "$uuid" = "$(mdadm --detail /dev/md53 | awk '/UUID/ {print $(NF);}')" ] && { echo MATCHED; unset uuid; }
MATCHED
#

And, well, not enough space left to add my comments here, so shall reply to this to continue that.