The key point loader needs to adapt to the hubble

1. When the loader is started, the security check of options will be skipped if options are passed in from outside
2. The metrics information of the loader needs to be recorded in a more regular way
3. The import progress (percentage) of loader, and the import time needs a convenient way to obtain
4. At the end of the loader, there should be a clear status indication, such as success, partial success, failure, etc

The issue names no files, tests, or entry points. Start by locating the key point loader and its option validation, metrics, progress, and completion-status code; then determine the design and tests needed for each requested behavior, including success, partial-success, and failure outcomes.

Written by the indexing model from the issue text.