If you are writing a modern Android app for late-version APIs, why would you want to use Android.App.Activity? You were right the first time with AndroidX.AppCompat.App.AppCompatActivity.
I don't know why the Android app template (either net8 or net9.0-android) defaults to Android.App.Activity because that is the first thing you would want to change it to AndroidX.AppCompat.App.AppCompatActivity.
AndroidX is for modern Android development. Look at the dependencies in that template; there is not a single AndroidX Nuget.
I suppose that template is just an example of MS trying to push people to Maui; either that, or they were just being lazy, or if you look at it another way, they are just introducing you to the .Net project structure.
I keep pointing you to my GitHub page, where you will find examples of what you need to convert from Xamarin.Android. As you can see, you don't need to rush to .net.
You may be better off keeping your Android app as Xamarin.Android. You are good (at least for another 12 months) with Android 14. It is only when you want to move to Android 15 that you have to convert to <TargetFramework>net9.0-android35</TargetFramework>
Most of those projects have examples of OnBackPressedCallback. If you don't have an Android 15 device, remember to turn Predictive Back Animations on in Developer Options. You also need android:enableOnBackInvokedCallback="true" in the AndroidManifest.xml.
The key points for predictive back. NavigationComponent, NavGraph, Single Activity and individual fragments with ConstraintLayouts for each screen.