Don't forget we are talking about a Snake
5e defines prone, and it aligns with the definition of prone in English. 5e is written in English.
In both 3e and 4e, you are supposed to treat keywords as magic tokens and mostly ignore what they mean in English. In 4e they even gave this advice explicitly in the rules text.
This is not how 5e is written. 5e is, first and foremost, an English text.
What is Prone?
From the 2014 PHB:
Combatants often find themselves lying on the ground, either because they are knocked down or because they throw themselves down. In the game, they are prone.
Snakes cannot become "more prone" - they are already lying on the ground. Making them "more prone" is nonsense. Applying the prone condition to a creature that is already lying on the ground should do nothing. Well, if the "snake" had wings, I would probably make it fall, as knocking things prone in 5e also knocks (non-hovering) creatures out of the sky.
It is consistent to invent a definition of "Prone" that isn't the English word "prone", but there is no huge balance effect here, but there isn't a need to do so.
Use common sense
Use common sense, and then double check it to ensure it doesn't break the game part of the game. By making it impossible to trip snakes, are you making a PC's entire build worthless? Are you breaking an entire game subsystem? Does this snake become an unstoppable python of destruction due to it not being possible to trip it?
If the answer to these questions is "no", simply state (as a DM) "you cannot trip a snake" and move on. If it turns out you ruled incorrectly (due to game balance reasons) you can fix it later.
I already mentioned that "knocking prone" is one of the ways to knock non-hovering creatures out of the air. As a DM you should be aware of this, and allow a flying creature to be "knocked prone" and hence fall - flying in combat in 5e is supposed to be dangerous to make up for its extremely powerful advantages. Creatures with "hover" ignores this, of course.
Standard State
While a snake is indeed lying on the ground, I wouldn't have the other mechanical effects of prone apply - halved movement speed, advantage and disadvantage on attacks, etc - because the Snakes stats already reflect what it is like to attack a Snake in its standard configuration.
Fluff vs Crunch
5e, unlike 4e, doesn't have explicit fluff distinct from rules text. The fact that knocking a creature prone actually makes them prone is part of the rules text, it is not fluff you are supposed to ignore.
Similarly the creature is "snake", not "creature with these game statistics with the word 'snake' taped to it". The 5e rules are some of the rules how to model the snake in the 5e combat engine, it doesn't mean you should ignore the fact the we are talking about a snake.
Try to start with "its a snake" when reasoning about the snake, not "it has these game statistics".
(The one big exception is that "an attack that defeats the creature" should mainly focus on depleting HP, and that non-lethal attacks and damage can represent things like "I grab the snake by its head so that it cannot strike".)
This isn't the only way to handle it
You could just houserule that Snakes get Immune: Prone in their stat block. That is fine.
You could also allow snakes to be knocked onto their back and call that "prone". This runs into the twofold problem that a snake on its back is harder to hit with ranged weapons, and that in reality Snakes can flip over much easier than (say) a human can get up from lying on its back.