No, and here's the actual difference
HDR merging, whether through Photomatix, Lightroom's Merge to HDR, or Camera Raw's own HDR merge, is algorithmic and global: software analyzes your bracketed exposures and blends them into one file using the same formula across the entire frame. You get one result, and your control over it comes from tone-mapping sliders applied after the fact, not from deciding pixel by pixel which exposure contributes where.
Luminosity-mask blending is manual and local. You build tonal selections and decide directly which exposure shows through in which zone: the bright sky comes from the darkest frame, the shadowed foreground comes from the brightest, and everything in between blends however you choose to shape the mask. It's slower, but every decision in the final image is one you made on purpose.
The noise problem HDR doesn't solve well
Tone mapping tends to amplify noise, and that gets worse fast when your bracketed exposures were shot at different ISOs or the shadows in your darkest frame were pushed hard to recover detail. An HDR algorithm blends all of that noise into the final result along with everything else. Luminosity masking sidesteps the problem by letting you choose, zone by zone, which exposure to pull from: use the cleanest, lowest-ISO frame for the shadows instead of accepting whatever noise the automated merge brings in from every bracket at once.
Where HDR fails outright: anything that moved
An HDR algorithm assumes every bracketed exposure shows the exact same scene. Clouds, water, moving branches or people between frames break that assumption, and the result is ghosting: soft double-edges or smeared motion where the algorithm tried to merge two different positions of the same object. Manual luminosity-mask blending doesn't have this problem, because you're selecting a single frame's rendition for that area, not asking software to average multiple positions together.
This is also why luminosity masks, not HDR merging, are the standard technique for sky replacement and perspective-blend composites: an algorithmic merge assumes all frames are the same scene at the same moment, which isn't true once you're deliberately combining different skies or different vantage points into one image.
Where HDR actually wins
For a static scene with a large but even dynamic range gap, no moving elements, and no need for local exceptions, an HDR merge is genuinely faster: one click versus building and refining masks by hand. If the tone-mapped result already looks right, or only needs light global adjustment, there's no reason to redo that work manually.
Quick answers to a few related questions
Does Lightroom or ACR's "Merge to HDR" replace luminosity masking entirely?
No. It's still a global algorithm applied to the whole frame. It doesn't give you the ability to paint a local exception into one specific area the way a hand-built mask does.
Can I combine both techniques?
Yes, and it's a common workflow: use an HDR merge as a fast base for scenes where it works well, then bring in a luminosity-mask touch-up on top for any specific area, like a moving element or a noisy shadow, that the automated merge handled poorly.
Is that flat, over-processed "HDR look" a result of the merging method itself?
No, that's a separate issue: aggressive tone-mapping settings, not the act of merging exposures. A well-tone-mapped HDR merge and a well-built luminosity-mask blend can both look completely natural, or both look artificial if pushed too hard.
EN
IT