Running the app on the newly released Wear OS 6 beta (API 36, based on Android 16) solves the issue. The warning no longer appears, which is the expected behavior. On Wear OS 5.1 (API 35) the error stills appears, so I assume Google fixed it in the new version only.