Air carrier First Officer reported an NMAC on approach to MCI following an unstabilized approach.

Narrative

The Approach Controller left us high and fast compared to the preceding Aircraft Y. We were instructed to slow and descend which we did. We were asked if we had the Aircraft Y in sight which we did as well as the runway. Our ground speed was roughly 35 kts. faster than the Aircraft Y as ground speed mini had our approach speed at 160 kts. Our spacing was roughly two and one half miles according to our ND. The Aircraft Y did not clear the runway with sufficient spacing and we were directed to go-around. While on subsequent vectors and turning base; ATC advised of VFR traffic that would be at our 12 o'clock position and 500 ft. below. That traffic was in sight visually; as well as on the TCAS. While on our base leg; that aircraft climbed to within 300 ft. and we received a TCAS RA with instructions not to descend. The autopilot was disconnected and level flight was maintained. Once we were clear of the conflict; automation was restored and we landed without further incident.MCI was operating on Runway 27 with high winds from the west. With this not being their normal two runway traffic flow; spacing issues could become more challenging. When we were given the instruction to slow and descend; a comment was made about the Controller having forgotten about us. It didn't help that the Aircraft Y was not able to make F or E as the Tower had hoped and then was instructed to expedite to C8. For the TCAS; the same Controller that didn't allow for enough approach spacing may have felt an earlier turn to base and final was a good way to help us out to make amends. After the initial base vector; he did shorten our turn by 10 degrees to allow us to pass behind the other aircraft; which would have worked had that aircraft maintained a VFR altitude.