I quickly checked the address range shown in IDA within the ida64.exe process using a kernel debugger, and the memory is question marks, indeed there is no VAD allocation for the range.
I don't want to reverse engineer IDA code, and I've searched for the byte sequence within the process using a kernel debugger, getting a match on the thread stack in the same exact place every time (0x17dc58) regardless of byte sequence searched, presumably due to the debugger attaching a thread to compare the byte sequence. It is taking too long to search the rest of the process, 8TiB of virtual memory, so where is it? On a heap? Clearly IDA must be pretending it is at whatever virtual address you base it at and transparently translates the virtual address to the real virtual address.
I want to do this because I want to check what is actually behind question marks in certain situations,like in the IAT where it shows question marks instead of the offsets to names