How do you set up VSCode to use an existing environment - powershell

Question

I have recently been using a combination of CMake and NMake from the Build Tools for Visual Studio 2022 package. I would like to integrate that with VSCode's task system but it appears to not be using the environment I have set up.
If I run cmake -B build in a Visual Studio 2022 Developer PowerShell instance in Windows Terminal it will generate an makefile designed to be used with NMake as I have set the environment variable needed to do that by default. I have changed VSCode's default instance of PowerShell to use the same arguments on start up so now if I run cmake -B build in the default VSCode terminal I also get a makefile designed to be used with NMake.
The problem occurs when I try to make a tasks.json task that calls cmake -B build for me, instead of generating an NMake makefile it defaults to a Visual Studio project. When I tried to add -G NMake Makefiles to the task arguments it failed stating it couldn't find NMake. I assumed this was because the tasks doesn't call the same startup parameters that a terminal does so replicated the same config I used for changing the VSCode's default terminal to the
Dev version but it didn't fix the issue.
My task:
"label": "cmake_setup_debug",
"type": "process",
"command": "cmake",
"args": [
"-G",
"NMake Makefiles",
"-B",
"${workspaceFolder}/bin/debug"
],
"problemMatcher": [],
"options": {
"shell": {
"executable": "powershell.exe",
"args": [
"-noexit",
"-command",
"&{Import-Module 'C:/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/Tools/Microsoft.VisualStudio.DevShell.dll'; Enter-VsDevShell 0d22feab -SkipAutomaticLocation -DevCmdArguments -arch=x64}"
],
}
}
Is it possible to force a task to use a specific instance of powershell with all the needed start up parameters?