I would say that tracking any issues coming on the interface/product is part of the job, I think you already know that! And if you want to be sure that the devs know it too, I advise you to have this short introduction of your role or just a reminder of it.
Something that sounds like “My goal here is not only to giving you a list of good and bad things but just discussing what happened during the test and what we should do about it.”
About the fact that you think they might think you skewed the data… Well, the only thing you have to do is to show that you are clear in your test and your data. Don’t hesitate to introduce the method, what the participants have to do, the data table you have… Anything that lets them see what you’ve done. That does not mean they will take a look at it, but it proves that you have nothing to hide (It depends on your situation, I’m currently an in-house UX Researcher so it could be different if you’re not your choice!).
I would say that you have to keep in mind that this is more an “Ok, Let’s see what people say, and what people do and why” more than just reporting it without anything else. It’s easier if you give not only the result but the food for thought that comes with it.
I’m not sure that’s pretty clear, don’t hesitate to tell me but if you take some time to explain to them what happened and why it will be less brutal!