Many thanks, Tony; and my apologies for delay in reply ~ I was waiting for an opportunity try out and report back. I have tried both adding the printer back, and reinstalling macOS Monterey via macOS Recovery. Unfortunately, the reinstallation failed twice, with the error-message "com.apple.Buildinfo.preflight.error error 21". After the first failure, I followed online-searched advice to run Disk Utility First Aid for the Macintosh HD, before retrying the reinstallation.
After the second failure, I tiptoed away from the new and perplexing issue of "preflight" indigestion on macOS Recovery (enough problems!

) and turned to suggestions given by Epson in response to my messaging them. Their first suggestion, to reinstall Epson's latest XP-202 driver for Mac after first uninstalling the old Epson software, has also not fixed the problem. Epson also suggest checking that the printer is connected to the same Wi-Fi network as my MacBook Pro: the printer's Wi-Fi light is on and steady, and I am unaware of any other network it could be connected to. Epson also suggest adding the printer via its IP address: though the printer appears on my MacBook's "Add Printer" list (which pops up on a new page after pressing "+" to add a printer to the blank section for available printers on the Printers & Scanners page), no IP address appears for it; but, theoretically, both the printer's Wi-Fi connection status
and its IP address would print out on the Epson printer's network status sheet...if only I could get one to print! It makes 'happy' printing noises, and the toner cartridges are OK, and I have head-cleaned it twice after its 1-2 years of inaction, but at best only illegibly faint stippling appears as the end result on paper. I do not know of another way to find the IP address for the printer.
So, at the moment, I am stumped, and have found two more problems ("preflight" indigestion on macOS Recovery; printer not printing legibly) in addition to my original one.

If I can get the printer to produce a legible network status sheet, maybe the IP address would help with the original problem...I will have to look in that direction first, I guess.