You said: "- A Notification (Tap) on Watch when Bluetooth from Phone disconnects (out of range), to prevent loss, and vice versa."
You should do that progammatically in your app. I do that in my real-time messaging app for doctors since they depend on the app for patient assignments. But a casual watch app may not want that.
If you prototype this with your app you will see that the connection can drop a lot for different reasons and remain disconnected for a long period of time. So there's no "across-the-board" way for Apple engineering to mandate behavior since:
1. that can easily overwhelm users with notifications
2. that would confuse everyone and especially accessibility users as your proposal is haptic only
3. that would go against the iOS and watchOS connectivity loss paradigm
4. a connection loss is an app issue related to "data availabilty" and not a system issue, so your propsal would have Apple engineering break apps which use the current app-centric paradigm like mine
5. Apple does provide watch connectivity status for users both in the control center seen with a swipe up from the watch face and on the watch face itself: