The problem with your ninja gaiden example is more the implementation of the feature. Enemies would be specifically placed in location where they'd knock you back off screen over an open pit far enough away they'd respawn as soon as you moved forward inevitably sending you to your death.
Also, i'm fairly certain it had more to do with the way the nes held the screens and enemy objects in memory than an intentional choice. Most games on the nes had respawning enemies once you returned to a screen. And after going through the source code for metroid, it's simply because of memory limitations.
The ninja gaiden developers took advantage of this by placing enemies in the most frustrating positions possible. I've beat all three of the originals a few times and i grew up playing the hell out of ninja gaiden 2, but that enemy placement is sadistic for the sake of it.
Also, i'm fairly certain it had more to do with the way the nes held the screens and enemy objects in memory than an intentional choice. Most games on the nes had respawning enemies once you returned to a screen. And after going through the source code for metroid, it's simply because of memory limitations.
https://www.metroid-database.com/source-code/
The ninja gaiden developers took advantage of this by placing enemies in the most frustrating positions possible. I've beat all three of the originals a few times and i grew up playing the hell out of ninja gaiden 2, but that enemy placement is sadistic for the sake of it.