What are ways/methods to replicate animation to all players w/F.E using CLERP?

With FilteringEnabled, you need to consider 2 methods:

• Replication state
• Replication event

State

Replication state is what Roblox defaultly uses. The entire state of all (modified) properties in the game is serialized and sent over the network. This includes details such as the physics state, for physics prediction. Without FE, the client also sends back their state, including all of their input and all of their data on the physics. This is combined on the server with a little authoritative logic (Who owns what; who knows what best; who touched this; etc) to produce what you're used to: Almost seamless networking with reasonable stability, and nasty messes with some things that replicate all the time.

Events

Replication events describe details such as when the server tells a sound to play. The server tells the client to play the sound in question, but the server has no clue if the client is even playing the sound or how long the sound is - The server never actually plays the sound. If an explosion happens, the server tells the client that an explosion happened and where, and then replication state normally sorts out the physics to accompany it. Animations, particles and various other methods all (should) use the same system.

How do you go about this?

Use replication events. Tell the clients when the animation starts and ends, and use a timestamp so that the client knows when the animation started, so that it can line up the animation with the other clients. Handle the animations locally, but make sure to tell the server, and make sure that the server tells the other clients. Don't rely on replication state to tell the client how the animation looks, because it'll lag and it won't play nice with the network.