I cannot answer to MS's plans for MFC but from my understanding it is not really a framework they are actively maintaining. Yes it ships with VS but so does ATL and only because these are the only frameworks for C++ that MS provides. Today if you were to ask MS about building a UI they are going to push you toward WinUI3 or .NET UIs like Maui or WPF (or whatever we're calling it today). Therefore I would be shocked if there is any investment in updating MFC beyond recompiling for the newer C++ libraries.
At the same time you have a compatibility issue as well. MFC is just a wrapper around Win32 and therefore the bulk of the functionality is provided there. MFC cannot just be updated to use functionality only available on newer OSes without breaking support for existing OSes and that would be a major issue for MFC. So I think the best option, outside of moving away from MFC if you need this behavior, is to use a third party library that might support it.
But 5 years ago someone tried to start making MFC support the Windows theme. You can read about their efforts here. Be aware though that there are going to be gaps and issues, lots of code to write and probably things that aren't going to work properly. The key is the CMFCVisualManager
class which is where the existing MFC framework is able to support some of the (new/old) Office themes back when Office was doing this. However I'm not convinced that just creating a derived type from that class will make everything work correctly.
Retrofitting a modern UI onto a legacy framework just isn't feasible. If you really want a modern UI then maybe you should consider updating the UI to a modern framework and leave your non-UI C++ code as is. They can work together. But this is just my opinion.