It work if you use a newer mke2fs:
% mke2fs -t ext4 -b 1024 /tmp/foo.img 472T
mke2fs 1.45.5 (07-Jan-2020)
Creating regular file /tmp/foo.img
Creating filesystem with 506806140928 1k blocks and 3959422976 inodes
Filesystem UUID: 64d8234d-68d8-42a8-9dba-414523184256
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409, 663553,
1024001, 1990657, 2809857, 5120001, 5971969, 17915905, 19668993,
25600001, 53747713, 128000001, 137682945, 161243137, 483729409,
640000001, 963780609, 1451188225, 3200000001, 4353564673, 6746464257,
13060694017, 16000000001, 39182082049, 47225249793, 80000000001,
117546246145, 330576748545, 352638738433, 400000000001
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: Done
You can probably make it work by adding -O 64bit to the mke2fs command, but there have been a huge number of bug fixes since the 1.44.x series, so my recommendation is updating to something more up-to-date. In particular, if you want to use online resize, especially with 64-bit file systems, DO NOT use the version of resize2fs with Ubuntu LTS. You really really REALLY want e2fsprogs 1.45.5. See the "bug fixes" section in the release notes.
specified blocksize 1024 is less than device physical sectorsize 4096
means your physical device exposes a sector size of 4096 and you can't create a block smaller than the unit size