But I wonder if just the fact that being in orbit, and the communication complications of the would make it logistically unfeasible.
As mentioned in comments to the OP, "feasible" may mean different things in different contexts. But technical feasibility is probably not the only important issue: economic feasibility is also important. It is not, yet, economically feasible.
There are several terrestrial applications for truly remote, near or completely unsupported telerobotic surgery. For instance, the Antarctic use case pointed to in the linked question, or in remote locations worldwide. If and to the degree the tech exists to enable that, it has not been deployed notwithstanding enormous human and financial costs of failing to have it in place. Note that the radio communication delays and complications terrestrially may be similar to the issues communicating with ISS.
During surgery, even if everything goes as planned, all sorts of things happen at unpredictable times. For instance, after initial incision and retraction, there may be blood in relatively unpredictable places or at unpredictable times that obscure views and potentially injure the patient. The surgeon needs to respond to those quickly. If there is significant latency in the transmission, the surgeon cannot do so. One way to deal with this is to have a surgeon on board ISS to assist the ground surgeon using the telerobot. But that is inefficient - easier to just have the onboard surgeon do the cutting with a consulting surgeon in her ear, following along by video. No need for the robot.
If the question is limited to technical feasibility, it seems to me that the first technical issue would be maintaining the communication link throughout orbit. This would require consistent and predictable connection between the two endpoints, which is complicated. Once a consistent connection can be maintained, the remaining issues are not unique to ISS: relatively high latency, possibility of blackout, unpredictability, and lack of human backup intervention in the event of an emergency all confront terrestrial applications - they are not special to ISS. So it seems to me the unique hurdle is maintaining communication in orbit. Put differently, if we could do it on earth (we can't right now, or we would be,) then the only impediment to doing it on ISS is maintaining reliable communication throughout orbit.
Maintaining reliable communication throughout orbit is certainly hypothetically possible. For instance, if obstructions were cleared and enough geosynchronously orbiting satellites hung in the air, we should be able to maintain line-of-sight with ISS throughout its orbit, and communication maintained. This is in the works - for instance, see this relevant question concerning end-to-end optical communication between ISS and a ground station.The significant variable latency is not unique - the telerobotic system must have a way to deal with unexpected events in the case when communication drops, and a way to recognize and prepare for latency. This probably means that the system needs to be backed by a powerful AI that can do things like recognize and clamp off unexpected bleeders.
Bottom line - if by "telerobotic surgery" you mean long-distance waldos, high and variable latency communication makes their use impossible or dangerous. If the telerobots have advanced with a significant AI, and if the communication problem has been addressed, then it may be feasible. At present, that is the stuff of (hopefully not far off) sci-fi.
It is feasible. Network latency is a challenge however it is one that is not unique to space. Although that is dependent on the length of the operation because having to reroute instructions across the planet to keep in contact with a moving vehicle would be a bit more challenging.
There is one major counter argument to its feasibility though. Normally when such robots are used there are medical personnel on standby in that location who can jump in in the event something has gone wrong. For instance, the robot could break down, power could be lost, the network could go down. This is still very much a problem and even more so in space where you only have your crew and a whole list of technical things that can go wrong.
That being said, I would see a robotic surgeon as a backup/skillset enhancement to the mission rather than a replacement for medically trained crewmembers. Say a crewmember gets impaled through the brain, I doubt they would have a neurosurgeon on board and he definitely wouldn't be stable enough for re-entry but they could just dial one up to try and stabilize him. Or say the medical personnel are injured and need stabilization.
Bottom line is, a capability that can increase mission success without adding much in the way of resource cost/allocation is always great to have.