ViewModels are designed to hold and manage a lifecycle aware (UI) component (i.e. activities and/or fragments) related data.
Normally you shouldn't save app context, activity, or view objects into ViewModel because ViewModels can live longer than the activity/fragment; because they can be destroyed and recreated on configuration changes; or by when the Android system decides to do that and in such cases ViewModel can hold stalled context/views of an already destroyed activity/fragment. So, ViewModel can update UI views that doesn't exist anymore.
When UI views (activities/fragments) are destroyed due to user/configuration change "such as screen rotation" or system action, their UI-related data will be lost; and ViewModel solved this issue by keeping this data on the event of those changes.
A ViewModel can be bounded to the data of an activity, an acrivity with its fragments, a parent fragment and child fragments, or to a single fragment. But it can't bound to the data of two different activity; and therefore it can't be inherited from the parent activity.
Starting a new activity should be initiated from the current activity not its ViewModel; the parent activity will stop accordingly, and consequently its ViewModel can't be accessed from the new activity.
Check this discussion for more info