So the esri community is aware of what they can do to properly REFERENCE and ESCALATE this bug with Esri: Login to your My Esri account and go here (BUG-000124749)
https://my.esri.com/#/support/bugs/BUG-000124749
Click Escalate with the number of users affected (many in our case) and business justification for escalation.
My understanding is that despite this bug being identified all the way back on 8/23/2019 with 2.4.x the issue was not resolved in 2.4.2 and is unlikely to be resolved in 2.4.3. I can only imagine this is because of priorities resulting from a lack of escalation. From my perspective - this bug produces VTPK files that our clients cannot use (we cannot zoom in on equipment like poles and fuses that are drawn close together spatially - the features completely disappear from the map as they start to spread apart and show labels) and a "workaround" of using the Desktop provides an unacceptable inability for our staff to fully automate (i.e. on a clock and with a computer, not with human hands) the scripted Vector Tile Package generation for the 18 or so regions we've compartmentalized across our company service territory. We must have this fixed and until we can we are stuck frozen on ArcGIS Pro 2.3.2 on our MMPK/VTPK generation machine which creates security exceptions and software incompatibilities across our enterprise as we try to keep up with the esri ArcGIS Pro releases for other GIS deliverables.
- PacifiCorp IT GIS Team
p.s. Example of the line of Python code we ran - the "0" isn't being respected (most examples use 70.5310735 which looks to be the internal default it is now returning in the VTPK files.)
arcpy.management.CreateVectorTilePackage(vtpk_map, vtpk, "ONLINE", "", "INDEXED", 295828763.795777, 0)