Hi James:
I have edited my post above in an attempt to clarify the workflow you reportedly used, and to apologize for my drawing / posting an incorrect inference: 
 https://www.fsdeveloper.com/forum/threads/removing-double-sided-faces.76400/post-927147
https://www.fsdeveloper.com/forum/threads/removing-double-sided-faces.76400/post-927147
I appreciate your efforts to contribute to troubleshooting the possible source of the Material mis-mapping incurred apparently during KMZ import / export.
However,  presently my available time and energy are rather limited, and my original goal when I saw your OP above in this discussion thread was to offer help to you and others who use Sketchup with resolving issues related to working with double-sided Faces.
Secondarily my goal was to address options to reduce 3D model geometry complexity via analysis of your original 3D model seen in your OP screenie above.
While I would like to ultimately ID the cause of the 'Material mis-mapping' incurred apparently during KMZ import / export when available time and energy permits, at this point, I believe it would be more appropriate to specifically address that 3D model shown in your OP, as it would properly be more "on topic".
The subsequent discussions which have ensued are certainly reasonably related as sub-topics, but would likely be best separated into a new discussion thread within the Sketchup forum.
I believe it would be preferable to re-direct the flow of this discussion back to exploring the basis for geometry complexity in your OP's original 3D model.
https://www.fsdeveloper.com/forum/threads/removing-double-sided-faces.76400/post-927034
IMHO, we all might wish to show our work at its best, particularly when we are somewhat new to a FS Developer support forum, but now that you know this environment is primarily focused on matters of mutual interest and concern, and most of us are sincerely trying to learn and to help one another, I hope you see a potential mutual benefit to posting the actual content that is the basis of a query when it is needed to offer a properly informed reply to a specific query.
Many here are developers of FS payware and may have issues of confidentiality under NDA's in a 'perceived' competitive niche market, and others may also have issues of pride in accomplishment as a result of hard-earned skills, which compels them to prefer not disclosing the content that is the actual basis for queries here at FS Developer, especially if they are initially uncertain about how to correct their development challenge(s) at a particular point in time.
We all may benefit from sharing ideas and development challenges, and IMHO, it is unlikely lasting damage will ensue from "showing one's cards" if asked.
I suggest that it is best to disclose the actual content that is the basis of a query- 'warts and all'- as a "work-in-progress" ...that will ultimately be revised.
While Dick suggested the option of attaching an "example" of content that shows the issue you were concerned about in your OP, I propose alternatively, if you still have a SKP for the 
original 3D model which was the basis of your OP above in this thread, that you please attach- or link- to it here.
I do not wish to offend you, but I believe that it is best to 
not rebuild and attach a "different" version of a project which was the basis for a query here.
Your new build of the 3D model indeed showed a significant enhancement of the "Poly" count; but I would prefer to also examine the 
original 3d model.
I would then like to address that specific geometry complexity issue to "stay on topic", while incidentally determining if double-sided Faces are involved.
We can then discuss additional related issues that may involve Material mapping (and/or "Material mis-mapping"), and start new threads as needed.
We can also discuss options to reduce geometry complexity via plugin Ruby scripts- and via MCX features- to save having to re-build a 3D model.
Thanks for considering my proposed re-direction of this discussion to IMHO, more appropriately address each sub-topic in order- and in context. 
 
GaryGB