Hrm how best to explain. Really what you are looking for is a corrupt firmware file in the redump of whatever you wrote that would not boot. Testing this on the dump of what would boot isn't going to help much. Only certain corrupt files will cause an explicit Exx error screen, while when others are corrupt or missing you get infinite boot logo or a boot logo that runs for a while then freezes suddenly.
The simple fact is that since 9199 firmware files have grown in size, and now take up more of your flash which is probably why you didn't see this problem in 9199. You keep mentioning that block 351 - what is the contents of it when you redump? If it's not 0x0 filled (especially in byte 0x205) but is also present in the remap area, often the console will ignore the remap and depending where the block is the result is precisely what you are seeing - in this case it's recommended to reflash the entire block with 0x0 filled data, and only that block.
Please run down your process and let us know how you are getting to a non-booting state, it may help someone spot something that is amiss.
If I correctly understood, I should write nand with remapping bad block to 3FF and the block 0x351 separately to erase with nandpro usb: - e16 351 1 ?
I`m write remapped nand and erase 351 bad block - failed
0x0 filled data on 351 - failed