It takes some planning before starting the edit. You want to do as many adjustments as possible using parametric/nondestructive methods stored in separate layers, so that all you have to do is drag those layers to another image and they adapt to the new content. This works OK when all of the edits can be done as adjustment layers, layer effects, or Smart Filters, all easy to duplicate to other images. But any edits that permanently alter pixels on the original image cannot be copied to another image…they’re “baked in.”
Some of the techniques that simplify bulk edits are easier for advanced users. For example, Blake Rudis pointed out that although a manually created (rendered to pixels) luminance mask cannot adapt to another image, an adjustment limited by BlendIf luminance controls will adapt to another image because it’s based on levels, not pixels.
If your images start out as raw files, then a better strategy would be to start by doing as many edits as possible in Adobe Camera Raw or Lightroom/Lightroom Classic. The reason is that those applications are fully parametric and nondestructive, so practically all adjustments are easy to sync or paste to other images, and many of them auto-adapt.
For example, if you retouched skin in Camera Raw or Lightroom by generating a People AI mask limited to skin, when that mask is synced or pasted to 10 other images with slightly different poses, the application AI re-analyzes the poses in the other images and auto-adapts the people skin mask for each of the other poses, saving much time. Photoshop cannot do this yet. Similarly, Camera Raw and Lightroom have proper built-in luminance range, color range, and now Point Color masks and those easily auto-adapt to other images too.
Camera Raw and Lightroom can’t do everything Photoshop can, so after the first round of quick bulk edits in CR/LR, any images needing further work could be moved to Photoshop for finishing.