Loading time / Loading screen?

I am not sure whether this is solely MPV issue or a mpv.net comes to hand, but I can attest to seeing delays also in pure MPV, so, mpv issute.

When I open a file in mpv, having 10 scripts in /portable_config/scripts and 3 conf files in /portable_config/scripts-opts, it takes considerable amount to "load", from OSC (modernx) to other behaviour. Simple "boss key" lua script won't start working until e.g. 1500ms passed since opening mpv.exe.

Is there some option, and could there be some option, to display "Loading screen" or simply to flash a message to user when all the lua scripts has successfully loaded?

mpv: v0.37.0-522-ga56d8ff1
os: Windows 10 22H2
hw: core i5m integrated graphics

Important Information

Provide following Information:

• mpv version
• Windows Version
• Source of the mpv binary
• If known which version of mpv introduced the problem
• GPU model, driver and version
• Possible screenshot or video of visual glitches

If you're not using git master or the latest release, update.
Releases are listed here: https://github.com/mpv-player/mpv/releases

Reproduction steps

Try to reproduce your issue with --no-config first. If it isn't reproducible
with --no-config try to first find out which option or script causes your issue.

If the issue is performance-related, try to reproduce it with --no-config
--profile=fast, which is designed to work on lower-end mobile devices.
Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut.

Describe the reproduction steps as precise as possible. It's very likely that
the bug you experience wasn't reproduced by the developer because the workflow
differs from your own.

Expected behavior

Actual behavior

Log file

Make a log file made with -v -v or --log-file=output.txt, attach it to
the issue, and replace this text with a link to it.

Without the log file, this issue will be closed for ignoring the issue template.

In the case of a crash, please provide a backtrace.

Sample files

Sample files needed to reproduce this issue can be attached to the issue
(preferred), or be uploaded to https://0x0.st/ or similar sites.
(Only needed if the issue cannot be reproduced without it.)
Do not use garbage like "cloud storage", especially not Google Drive.

Start by reproducing the delay on Windows with the reported scripts and configuration, then compare it with --no-config as requested by the issue template. Inspect the startup and script-loading paths once the cause is isolated; done would mean a user-visible loading indication that reliably reflects completion of script loading.