Refactor doom/reload

+ Remove non-interactive use-case (no more relying on the server; too
  unstable).
+ Ensure autoloads are properly reloaded (and thus, the load-path is
  properly repopulated).
+ Provide feedback when it's finished

core/autoload/help.el

@@ -234,22 +234,11 @@ necessary), reinistalize doom (via `doom-initialize') and reloads your private
 init.el and config.el. Then runs `doom-reload-hook'."
   (interactive "P")
   (require 'core-cli)
-  (cond ((and noninteractive (not (daemonp)))
-         (require 'server)
-         (if (not (server-running-p))
   (doom-reload-autoloads force-p)
-           (print! "Reloading active Emacs session...")
-           (print!
-            (bold "%%s")
-            (if (server-eval-at server-name '(doom/reload))
-                (green "Done!")
-              (red "There were issues!")))))
-        ((progn
-           (require 'core-packages)
-           (doom-reload-autoloads force-p)
-           (doom-initialize 'force)
+  (setq load-path doom-site-load-path)
+  (let (doom-init-p)
+    (doom-initialize))
   (with-demoted-errors "PRIVATE CONFIG ERROR: %s"
     (doom-initialize-modules 'force))
-           (print! (green "%d packages reloaded" (length package-alist)))
   (run-hook-wrapped 'doom-reload-hook #'doom-try-run-hook)
-           t))))
+  (message "Finished!"))