IMHO, you need to learn how to use a viewmodel that is strong type to a given view.
https://www.dotnettricks.com/learn/mvc/understanding-viewmodel-in-aspnet-mvc
https://deviq.com/other/kinds-of-models
You can have more than one model, a class in a viewmodel that is a class.
You have a view for Apple a view for car, etc and etc.
You can send in one viewmodel for all the views, but you know when you are using a view for apple so you configure the view for apple to use the apple model within the viewmodel. This thing about a base class a model in the viewmodel is suspect, and it would not pass a professional code review with each model having all the required properties for each model.