Not at all, because the module file is somewhere hidden deep inside the EXE file, and it's compressed as well. There is no special case to handle EXE files created with XM-EXE, because those EXE files are essentially a black box OpenMPT cannot look into.
What ModPlug Tracker did in Jedinhopy's case was assuming that the EXE file was a headerless Ultimate SoundTracker module - if the file sufficiently looked like a SoundTracker module, it would load it. Of course the file would just contain random noise because that's what an EXE sounds like - there was no secret module hidden inside that EXE file. SoundTracker module have no magic bytes so telling them apart from EXE files or MP3s is really hard work.
The heuristics for detecting whether some random binary data is a SoundTracker module have been tightened in the last few years, in particular so that libopenmpt doesn't claim to be able to play files which it should not play. This is important because libopenmpt can be used in other libraries and tools like XMPlay, Winamp, foobar2000, FFmpeg, etc, and those tools are able to decode a great variety of other file formats - but that doesn't work if libopenmpt claims to be able to play every random binary file, even if it technically can't.