Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base. This bug is only happening once in a specific project (and scene). Plus it seems the project has been opened with Unity 6 and then reopened with 2022.3 which seems to be the cause of the problem. Even though we are trying our best regarding backward compatibility, this is not something we support by default. Multiple reasons for that: Breaking API can be added between major versions, packages that might not be compatible, format of data storage that can change and not be compatible with the previous one... Regarding the specific case here and the unique repro on a single scene, we will close this ticket to prioritize other bugs.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.