test_for_nans wiped out in Stable Forge, worth restoring?

Nobody has claimed this yet.

Migrated a utility from Automatic1111 API to Stable Forge API and noticed that existing logic to detect failed all-black image results continues to work in Automatic1111 but not Stable Forge.

Digging into the code it's because the test_for_nans check is just returning in Stable Forge:
https://github.com/lllyasviel/stable-diffusion-webui-forge/blob/4d75507c3d6687439af17d342234bd885be71e03/modules/devices.py#L97
vs
Raising Nans exception in Automatic:
https://github.com/AUTOMATIC1111/stable-diffusion-webui/blob/82a973c04367123ae98bd9abdf80d9eda9b910e2/modules/devices.py#L242

Was this wiped out for a good reason? I can submit a pull request restoring this useful functionality but wanted to verify it's something that is still desired and not prevented by other functionality changes?

Start in modules/devices.py at the cited test_for_nans implementation, then compare it with the referenced Automatic1111 implementation. Determine why the check returns in Stable Forge and whether restoring the exception behavior is compatible with the surrounding functionality. Done means reaching a maintainer-backed decision and, if restoration is wanted, verifying the failed all-black image case.

Written by the indexing model from the issue text.