lol!

The Developer Help page for Editor.TraceBoundary (https://help.autodesk.com/view/OARX/2023/ENU/?guid=OARX-ManagedRefGuide-Autodesk_AutoCAD_EditorInput_Editor_TraceBoundary_Point3d__MarshalAsUnmanagedType_U1__bool) seems to have a mistake, they say:

In this case, the last entry is the outermost boundary, and the succeeding entries represent the islands found.

The sentence is obviously self-contradictory, but if one is to take just the key part (the last entry is the outermost), he will take away the wrong part! In fact, the first entity in the set is the outermost one, and the succeeding ones (as is written correctly) are the islands. Just a fun little mistake I stumbled upon this morning, so beware! 

This could be of a use . 

Code - Auto/Visual Lisp: [Select]

1. (defun c:test (/ l p)
2.   (while
3.     (setq l (tblnext "LAYER" (null l)))
4.      (setq p (cons (entmakex (list '(0 . "POINT")
5.                                    (list 10 0. 0. 0.)
6.                                    (cons 8 (cdr (assoc 2 l)))
7.                              )
8.                    )
9.                    p
10.              )
11.      )
12.   )
13.   (repeat 3
14.     (vla-purgeall
15.       (vla-get-activedocument (vlax-get-acad-object))
16.     )
17.   )
18.   (foreach x p (entdel x))
19.   (princ)
20. )

I would suggest to vla-copy the layers into dbx and then copy them back after purging the dwg.

If you are using CIV3D run Purgestyleandsettings maybe twice before normal purge. It makes a big difference.