The bug
/chunk
does not use the sender's dimension. For example, running the command "/chunk force 0 0
" while in the nether will load the targeted chunk in the overworld.
"/execute in the_nether run chunk force 0 0
" also defaults to the overworld.
Side note: When the second command is fixed, "/chunk in <dimension>
" becomes somewhat redundant.
Can confirm