Ok so being on the path of self soothing.....

…..I uploaded this map, the bike is running much cooler and unrestricted on freeways
I tried both tunes: first the Claviger one....found intro be very smooth, little hotter than stock 20773.... but felt engine was louder and running dry....I have ram air and tors by the way in 2015 r3r! And PCV at stock map, non zero values.
Then, I uploaded Hanso’s one with unrestricted settings, but enabled the O2 check box....And made PCV to all zero values.... took it de test ride, the bike was very smooth on high speeds, ran way cooler and very fast forward....but at slow speeds, it gave me a jerk every time I released the clutch....was not very pleasant on slow speeds....
On both maps, never heard any popping.....so what could be a middle ground here??????
Hmm, I'm no expert, I just share my experience and try to help folks move forward until the calvary shows up. ;^)
1. These TuneECU maps are not meant to be used with PCV. You indicated it was connected and had a map loaded with Clavigers tune. Maybe disconnect PCV and try his again.
2. Are you doing the ISCV reset and 12 minute tune (12 minutes AFTER the fan first kicks on)? It will take the ECU awhile to get acquainted with a new tune.
3. O2 sensor needs to be OFF or it will be fighting the maps settings at lower speeds - double click and remove checkmark or right click and select disable before downloading.
As per Claviger wrt O2 sensor removal and bung hole plug:
First off, why it's best to remove it: They are a sensitive device, the temperature is controlled to be in a narrow window for max life span, moisture is the devil for O2 sensors and it's disabled in software and left in the bike moisture can kill it.
Second, as to why it's better turned off: Triumph tunes only use it at low RPM low opening, and they shoot for a 14.3ish AFR, nothing wrong with that to be honest. Read on how narrow and sensors work, they don't measure the afr, they count how many " too rich" or "too lean" incidents it has over a time span and add or remove fuel to compensate. The result is an engine that's never right, instead it swings back and forth across the target lean to rich, but never right.
The range of the swing depends upon how fast the ECU updates the sensor value and does the man. The rocket ECU does both sampling and math pretty slowly, the result is a chunk chunk chunk idle, when you turn it off and set the AFR slightly "too rich" in the mid to high 13:1 range idle will be dead steady and stable.
Additionally if you were to make changes in your F and L tables, and the sensor is turned on but you don't change the AFR target to deactivate closed loop, it'll slowly trim both short and long term trims. The problem with that is that those trims are not limited to the closed loop areas but are instead applied elsewhere in the map too. It effectively undoes any custom ECU work you have.
Add in a PC-V and then there's another layer of computer fighting the ECU which is already fighting the work you've done.