I think I may have found a fix. Not to the problem, but just a fix to be able to open my photos.
I opened the current Photos app, went to settings within the app window, scrolled down to where it has an option to download and use Photos Legacy and downloaded it. Once it was installed, I clicked on any photo and that asked my what app I wanted to use to open it. I chose the Photos Legacy app and then checked the box at the bottom to make that my default. Seems to be working so far.
We will see how it shakes out in the long run, but THIS solution worked for ME. Everyone's computer is different, and I don't even know what was causing this issue in the first place, but it worked. I would encourage people to try this solution and see if it works for them.
The reason I have high confidence in this solution not being temporary is that it resolved the "not implemented" error during my current session of Explorer, ie not having to restart it from task manager. Nothing I have done prior accomplished this. Seriously, all I did was confirm I was still experiencing the issue in my current session, install the legacy Photos app, set it to default within settings, and ta da all my photos opened normally again.
I did try the default viewer trick with the current Photos app, and this did not work. It was after reading people saying that still didn't fix the problem even after reboot that I went with the above solution. It's a good thing I didn't reboot too; it wouldn't have given me the immediate gratification of the issue disappearing with the install of legacy Photos. I'm also not particularly keen on the redesign, problems aside. So I have no qualms with reverting. :)
If this solution does solve people's issues permanently, then it's clear the issue arose from the recent photos update. I don't know how I started experiencing it BEFORE installing the update, but maybe Windows implements some changes in an update before you actually restart to install it. I can't remember if the UI change had been implemented before or after I installed the update, and before or after the issue arose.
I'll keep posted if this solution sticks, but I'm optimistic.