[Suggestion] Show if rewind and run-ahead are enabled/disabled in log file + show the current display driver much earlier.

Hey!

It would be REALLY helpful for troubleshooting if we could have important stuff listed in log file as soon as the core is loaded, a few things like rewind, run-ahead and current video driver should be displayed CLEARLY and ASAP, for example:

[INFO] === Build =======================================
[INFO] CPU Model Name: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz
[INFO] Capabilities:  MMX MMXEXT SSE SSE2 SSE3 SSSE3 SSE4 SSE4.2 AES AVX
[INFO] Built: Nov 22 2020
[INFO] Version: 1.9.0
[INFO] Git: 865303c501
[INFO] =================================================
[INFO] [Display]: Found display driver: "vulkan".       <-- Should be on top or at least in the first few lines.
[INFO] Rewind is disabled.                              <-- These 2 are super important IMO,
[INFO] Run-ahead is enabled.                            <-- as they're often the cause of crashes.
[INFO] [Input]: Found input driver: "dinput".
[INFO] [CORE]: Loading dynamic libretro core from: "D:\programmes\RetroArch\cores\mednafen_psx_hw_libretro.dll"
[INFO] [Overrides]: No core-specific overrides found at D:\programmes\RetroArch\config\Beetle PSX HW\Beetle PSX HW.cfg.
[INFO] [Overrides]: No content-dir-specific overrides found at D:\programmes\RetroArch\config\Beetle PSX HW\CTR - Crash Team Racing (USA).cfg.
[INFO] [Overrides]: No game-specific overrides found at D:\programmes\RetroArch\config\Beetle PSX HW\CTR - Crash Team Racing (USA).cfg.

The line [INFO] [Display]: Found display driver: "xxxxx". actually already exists, but it's often buried in the middle of the logs and can be hard to find... so it would be great if it could be printed waaay sooner.

There's also a hint for rewind currently: [INFO] Initializing rewind buffer with size: 20 MB, but with PPSSPP core for example, it crashes BEFORE the line is printed, so yeah... 😅

Start by tracing the existing "[Display]: Found display driver" and rewind-buffer log messages through the startup sequence, then identify where run-ahead status is available. Done means the display driver appears near the beginning of the log and rewind and run-ahead enabled or disabled states are clearly recorded before core loading can fail.