Your source code is a nightmare, buddy ... sorry but I've never seen such a paradox coding with conditions here and there and if clausels all around messing up each other instance on their own.

Not only that you did not include any of the assembly files needed for the compiler, you also made some questionable choices in terms of "pawns either dead or alive", when scripting alternative ways of upload pawns and Co - what happens with them afterwards.
It is not possible to make a differnet foreach count and NOT replacing the current (for whatever reason this decision was made by you, I just don't get it ...) e.g. VX3 chip with a VX0.
Setting a condition as "leave VX2 / VX3 as is" will make the option "upload and leave body behind" invalid and turn it literally into the first option "do nothing, dublicate pawn" while leaving the chip as is.

Since this ain't working and I am not willing to dig through this messy code, the XML file instance ain't better in any regard.
Adding the simple
<RecipeDef ParentName="SurgeryRemoveChipBase">
<defName>ATPP_RemoveChipVX0</defName>
<label>Remove VX0 neural chip</label>
<description>Remove the VX0 neural chip, allowing the host to install other neural chips.</description>
<descriptionHyperlinks><ThingDef>ATPP_VX0Chip</ThingDef></descriptionHyperlinks>
<jobString>Removing neural chip.</jobString>
<removesHediff>ATPP_VX0Chip</removesHediff>
</RecipeDef>
Code does literally nothing. It won't show up. It will not let people uninstalling the VX0 chip (or any other, respectively changed and adjusted, VX1 to 3 chip).
And yes, this script does work, as I was able to remove a walk speed implant from another mod, which had also lacking removal surgery recipes.

Would be great, if you could simply fix this stuff.