It's a workflow that doesn't make sense.
Both Photos and LRC occupy the same place in the workflow. They are both media managers that use parametric editing that rely on a database to work. Both databases are proprietary and so they do not speak to each other. The Edit In feature assumes that there is one manager and it sends the image to a pixel editor and receives the edited version back. The media manager creates the file and receives it back. That's how it tracks the edited version.
A Raw file is different. It's not even a file really, just a sensor dump from the camera. You cannot save a raw file. Every time you process (or edit) it a new file is created... by the editor, not the media manager. It's effectively a 'Save As' command. So the manager has no way of keeping track of the edited file.
If you did send a Raw to LRC ti would have to be imported, processed and then exported (as the new file), so no manager could track that. As opposed to sending a jpeg to a pixel editor where it's just a simple Save command.
As both Photos and LRC are media managers with parametric editing the bit that makes no sense is trying to use one as a pixel editor, which it is not. Better to pick one horse and ride it.
For my money, and yours, LRC is a far more powerful app, more capable and you're paying for it every month. I'd use that rather than the giveaway that is Photos. If you want to use the Cloud features of Photos then after processing I would export from LIghroom to a folder, then import them to Photos for that.
The alternative? Export the original from photos to the Finder. Import it to LRC. Process it. Export the resulting image to the Finder and then Import it to Photos. What you then do with the copies of the original in the Finder and in LRC, and the copies of the exported version, is up to you.