I suspect you could get away with 'sending' ICSP code pretty safely with appropriate buffering and worst case reset/write timing, however the verify pass would require a bit more thinking to be sure each processor is at the party..
Perhaps if this is really necessary without a bootloader, your code could execute a code verification before 'running' - and 'not' blink a LED or whatever to let you know a specific processor is not actively participating.
Why multiple processors running the same code in close proximity in a dirty, high-rel environment?
Other than a very specific application, I can see many ways this might go wrong.
Let us know what you come up with!