Additional SQL Server features and topics not covered by specific categories
Let's assume for a second that it would be smoother to move to SQL 2019 than to SQL 2022 because of some changes. But what would the point be? You would have to move from SQL 2019 at some point, and you would encounter the same issues at that point when moving to SQL 2022 or some later version. So why not just as well take the pain directly? Also, if you move to SQL 2019, the next upgrade will have to be closer in time than if you go to SQL 2022. SQL 2019 will go out of mainstream support in less than 18 months.
As it stands, there are very few changes that are likely to cause any direct issues with SQL 2022. The only one I can think of is if you are using the Machine Learning Extensions. In difference to SQL 2016, SQL 2017 and SQL 2019, SQL 2022 does not ship with R (and Python), but you need to download and install it separately. And, oh, the free-standing Machine Learning Services has been removed completely. But these are not features that all sites use.
Another change is that Stretch Database has been deprecated for future removal in SQL 2022, but it is still there. In any case, no one in his sane mind would use Stretch. (Because it's far too expensive.)
What can bite you, no matter you go to SQL 2019 or SQL 2022 and also change the compatibility level to the latest version is that some optimizer enhancements lead to queries regressing in performance. You should have Query Store enabled on the database for a month before you upgrade. Then if you get a regression, you can force the old plan as a quick measure, and then you can investigate why things went wrong.